AI engineering and support for your connected product.

Get AI help with hardware and firmware, product adoption or technical support. Work privately or invite a specialist into team chat.

AI hardware and firmware assistant

Equidna

Work through circuits, board interfaces and Linux integration.

AI technical support

Pingüino

Investigate devices, logs and connectivity.

AI customer success

Nutria

Plan adoption and get more from your product.

An LED on a Pi 5. A control in your product.

Ask the AI hardware and firmware assistant, Equidna, how to connect an LED to your Raspberry Pi 5 I/O board and wire the software into Dataplicity.

  1. Work through the circuit. Check the board revision, GPIO mapping, LED polarity and current-limiting resistor.
  2. Build the Linux side. Define the GPIO application, permissions and startup behaviour.
  3. Connect the product control. Define an allowed on/off action, reported state and the bench test.

Example engineering task. Bring the board drawing and component specifications; verify the wiring and result on your hardware.

Explore hardware and firmware help →
Example GPIO LED circuitA 3.3 volt GPIO output connects through a series resistor R1, shown as an example one kilohm, to the LED anode. The LED cathode returns to the board ground. Outward arrows mark light emission. Check the actual I/O board pinout and component ratings.Example LED output3.3 V GPIO · active highPi 5 / I/OGPIO outGNDR11 kΩ*AKD1 · LED
Dataplicity controlLinux GPIO application
*Example resistor. Confirm your I/O board’s pinout and LED ratings.

Start with the work in front of you.

AI hardware and firmware assistance.

Work with Equidna through the circuit, GPIO application and Dataplicity integration using your actual board evidence.

AI hardware and firmware assistant

Equidna

24/7 AI help has plan and usage limits. Invite a specialist with chosen context for read-only team discussion; private operational help has separate authority. Human escalation is asynchronous.

Setup and technical guides ↓

Setup and technical guides

Choose the setup question or guide you need.

Detailed workflow and operating states

Illustrative operating sequence. People choose the scope and intervention; configured collection, rules and device behaviour supply the evidence.

  • Step 1 · Work from a real product requirement

    Provide the customer job, operating constraints and what your application already does. Nutria can help connect the requirement to supported product data, controls and customer experience. Supply external designs and unique requirements; they are not automatically known.

  • Step 2 · Connect hardware to software

    The AI hardware and firmware assistant, Equidna, works from the exact board/revision and supplied schematics or netlists through the Linux interface, permissions and product integration. Review uncertainty and define a bench test; guidance does not certify hardware.

  • Step 3 · Bring the specialist into the discussion

    In team chat, called Casa del Pingüino, invite an offered specialist, choose whole-conversation or selected-reply scope and whether earlier history is included. Teammates can retain the confirmed design decisions and next tests in the conversation.

  • Step 4 · Investigate through the permitted path

    For device evidence and supported operational actions, use the appropriate private support conversation with Pingüino. Review the proposed scope and action, then check the resulting state. A room invitation does not unlock those actions.

Work through the product with your teammates.

Illustrative team request, not a captured transcript or an assistant execution result.

  • Firmware engineer

    “Our controller operates locally. We need to expose settings and report whether a requested change happened.”

  • Product owner

    “Customers should see only their own machines and know when a change is waiting for an offline unit.”

  • Choose context, then ask for testable next steps

    Invite an offered specialist into team chat, called Casa del Pingüino. Choose conversation or selected-reply scope and history. Ask it to separate responsibilities, integration points, uncertainty and bench tests. Shared help is read-only under sponsor authority; invitation does not grant unrestricted account or device access.

    Team chat and specialist invitations →
Move to the permitted private path for operating evidence.

A shared conversation and private operational assistance have different permissions.

  • Investigate the selected equipment

    Use Pingüino’s private support path for permitted device/fleet evidence. Review supported action proposals, target and authority before approval, and verify the result afterwards.

    Follow the full device investigation →
  • Give hardware work its own attention

    Equidna connects supplied board evidence to firmware, Linux interfaces and product behaviour. No deployed fleet or separately programmed chatbot is required to begin the design discussion.

    Hardware and firmware engineering →
What you do not have to reconstruct between tools

Platform knowledge and explicitly granted context support the discussion. Invited room specialists use sponsor authority and granted conversation/history; shared-room help is read-only. Linked documents, boards, canvases and account objects are not all automatically readable.

  • Keep the responsibility clear

    24/7 AI assistance; plan and usage conditions apply. This is not 24/7 human staffing or an uptime SLA. Human escalation is an asynchronous support ticket where offered. An assistant suggestion is not execution evidence, a repaired device or a qualified design.

What would we need to change?

Configuration, product engineering and subscription eligibility are different requirements.

  • Enable and configure

    Use the existing specialist chooser or team-room invitation. Supply relevant requirements, exact hardware evidence and redacted findings. Choose context deliberately and keep private device operations in the supported private path.

  • What you keep

    Keep your engineering team, design tools, firmware, application and validation process. Assistance can precede agent installation and span any adoption path; it is not the final upgrade tier.

  • Plan and readiness

    Equidna and Pingüino are web-app specialists for Standard, Business+ and Enterprise within configured access. Free and Device Access have bounded guidance and different specialist choices. Team conversations are a paid capability; mobile technical help uses Delfín. Check the chooser and usage notice.

    Read the guide → →
The tools underneath the job

Use the exact implementation guides to check the supported contract and limits.

Bring a specialist into the work

Ask for help where evidence or an integration decision is unclear. Use the context and permissions available to that conversation.

  • Hardware, product and operations help

    Equidna helps connect supplied hardware evidence to the software path; Nutria helps plan the customer job; Pingüino helps investigate authorised operational evidence. Shared-room help remains read-only. 24/7 AI assistance has plan and usage conditions.

    Read the guide → →
Choose one useful result to prove.

Use the reference to build your own test. Validate the hardware, integration and operating process on your product.

  • AI hardware and firmware assistance

    Review the procedure and qualify the parts your product requires.

    Read the guide → →
  • Check adoption requirements

    Start with the product you have, then choose independent optional paths.

    Read the guide → →

Start with this job.

Use the existing specialist chooser or team-room invitation. Supply relevant requirements, exact hardware evidence and redacted findings. Choose context deliberately and keep private device operations in the supported private path.