Skip to content
Tallyfy
Developers

Apptronik Apollo humanoid robots

Where Tallyfy fits around an Apollo robot

Section titled “Where Tallyfy fits around an Apollo robot”

Apptronik makes Apollo, a humanoid robot aimed first at logistics and manufacturing ↗[2]. As of October 2026, it publishes no way for other software to send work to an Apollo or read what the robot is doing. Its contact page offers only a general enquiry form ↗[3]. So Tallyfy can’t talk to the robot.

Tallyfy can still run the written procedure for the people around it. That means who checks the work area, who signs off, and what gets recorded. A person carries each result into Tallyfy.

What Apptronik makes today

Section titled “What Apptronik makes today”

As of October 2026, the current robot is Apollo 2. Apptronik unveiled it on June 30, 2026 ↗[4] in two versions. One walks on two legs. The other rides on a wheeled base.

It isn’t a finished product. In a trade press interview ↗[5] published that day, Apptronik’s CEO called Apollo 2 a “prototype” and a “data collection platform”. Apptronik’s own announcement ↗[6] says the robots gather training data at its Austin site, at its research partner Google DeepMind, and at customers such as Mercedes-Benz and GXO. It names Apollo 3 as its “next-generation commercial product”. The announcement gives no date for it.

Jabil agreed in February 2025 ↗[7] to build Apollo robots and pilot them in some of its own factories.

Apptronik also makes the software. Its Apollo 2 page ↗[8] names two products, and neither has public documentation. Artemis runs on the robot. Fleet Connect is for the team in charge. Apptronik says it lets them watch robot status, hand out tasks and collect data across a fleet.

What outside software can ask an Apollo to do

Section titled “What outside software can ask an Apollo to do”

Nothing public exists as of October 2026. Apptronik publishes no API (a way for one program to talk to another), no developer kit and no developer documentation for Apollo. API Evangelist, an independent catalogue of company APIs, reached the same answer in May 2026 ↗[9].

For a written procedure, that means:

  • A Tallyfy step can’t start a robot task.
  • The robot can’t complete a Tallyfy task or send in a reading.
  • Fleet Connect may know what each robot is doing, but Apptronik doesn’t say whether other software can connect to it.

If you pilot or buy Apollo, ask Apptronik in writing what your own software may connect to. Until then, plan for a person in the middle.

Where a written procedure fits

Section titled “Where a written procedure fits”

Your people still work around the robot. Someone gets the area ready, someone watches the shift, and someone decides what to do when the robot stops. You can run those steps in Tallyfy:

  • Write the steps once in a template. Each launch becomes a process with its own tasks, assignees and deadlines.
  • Collect what people see in form fields.
  • Use an approve/reject task where someone has to sign off.
  • Report an issue on a task when something goes wrong. The task can’t be completed until it’s resolved.
  • Open the activity log on any process to see who did what and when.

When the procedure changes, edit the template. New launches use the new version. Running processes keep the one they started with.

Three examples of procedures you might write:

  • An area check before the robot works somewhere new.
  • A shift handover between supervisors.
  • A stop report each time a person has to step in.

How the pieces sit together

Section titled “How the pieces sit together”

This diagram shows who talks to what when a procedure runs beside an Apollo.

How the pieces sit togetherTallyfy templateTallyfy processYour teamApptronik softwareApollo robot Launch Tasks and resultsManages robotsRuns tasks

What to notice:

  • No arrow joins Tallyfy and Apollo. Nothing public exists to carry one.
  • Your team is the link. They get tasks from Tallyfy and record results there.
  • Apptronik’s own software sends work to the robot.

Technical details

Section titled “Technical details”

(Skip this unless you’re setting up the technical side.)

As of October 2026, Apptronik’s website mentions no SDK (a developer kit), no API reference and no ROS (Robot Operating System) interface for Apollo. That includes the Apollo 2 page ↗[10]. A GitHub organization called Apptronik-Public ↗[11] links to apptronik.com and holds no public repositories.

Tallyfy has an open API and webhooks, which are messages Tallyfy sends to another system when something happens. Both need software on the robot’s side to call or receive them. Apptronik documents none.

The Apollo 2 page gives no height, weight or payload. It does describe swappable batteries, a zone where the robot pauses if it detects an object, and a chest display that shows robot status, battery level and task progress.

Older figures of 5 foot 8 inches, 160 pounds and a 55 pound lift come from the 2023 announcement ↗[12] of an earlier robot. Apptronik now lists that robot as Apollo 1 ↗[13].

Section titled “Related articles”

Integrations > Robotics

Tallyfy has no integration or partnership with any robot maker. This concept section shows how a…
Get in touch
About Tallyfy