Skip to content

upstratus documentation

Record labelled examples with your phone, train a small model on our GPUs, and download a package of plain C for one of six supported microcontroller boards. You then build and flash that code with the board's own tools: upstratus does not flash boards for you yet.

Get started For AI Agents

What you can do

  • Collect data

    Scan a QR code with your phone and record motion or sound in the phone's browser. There is no app to install. Sensor readings from a data logger can be imported as a CSV file instead.

  • Train a model

    Pick a recipe on the Design screen, or describe the task in a sentence and get one suggested. The report tells you which labels the model confuses. It does not quote an accuracy your data cannot support.

  • Download C for your board

    Package a trained version for a board and download a zip of C source: the model and the kernels it runs on. See Supported boards for the six boards and what each one needs.

  • Read an error

    Every API error carries a code and a link to its entry, which says what it means and what to do next.

What upstratus does not do yet

These docs describe only what the product does. These things are not built:

  • Flashing a board from the browser. The Collect screen's Connect board button is disabled for this reason. You flash the downloaded code with your own tools.
  • On-device signal processing in the package. The downloaded C runs the model on a window of features that has already been computed. Your firmware has to compute those features from the sensor.
  • Live labels from a board and trying a trained model on your phone.
  • A published API schema. A small set of endpoints accepts an API key, but no OpenAPI description of them exists yet. See For AI Agents.

How these docs stay accurate

The pages are Markdown in the product's own repository and are built by a command. The Supported boards and Error codes pages are generated from the same registries the product reads, and a test fails if either page falls out of date. These docs have no screenshots yet: the screenshot pipeline captures them from automated QA runs, and that pipeline is not connected to upstratus yet.