Skip to main content

​
What Orbit is

Parsaa Orbit is the other half of Parsaa. The macOS app works on the code in front of you. Orbit works on the app you already shipped: crashes from real devices, MetricKit vitals, sessions and screens, test runs, build logs, App Store state, product analytics, and pull request reviews. It has two parts:

The console

A web console at platform.parsaa.app, one project at a time, with a page per surface.

The Apple SDK

A Swift package with no dependencies. Add it to your app and it reports what Apple already knows about it.
Nothing in Orbit is a second account. It signs in with the Parsaa account you already have, and it spends the same credits.

​
One login, one ledger

Your Parsaa account owns identity, your plan and your credit balance. Orbit verifies that account and never mints a login of its own, and it never keeps a second balance: the Usage page reads the Parsaa ledger and shows you what Orbit debited from it. That has one practical consequence worth knowing up front. Ingestion is free. AI is what costs credits.
Uploading a crash report, a build log, an .xcresult, an Instruments .trace or a compliance scan never debits a credit. Neither does reading anything in the console, or letting the SDK send telemetry. Only an AI action you ask for spends, and it prices itself before it runs.
Every AI action follows the same four steps: the page estimates the cost on render, running one opens a confirm step naming the cost and your balance, nothing is charged until you confirm, and the result lands with the model and the credits it used printed under it. A run that fails, or that the model refuses, is not charged.

​
Tiers and what each unlocks

Your workspace tier decides which surfaces answer and how far back they read. It comes from your Parsaa plan.
Free is the demo, and the demo does not run the model. A Free workspace can read every surface it has and upload evidence by hand, but POST /v1/ingest/* is answered 402 for its SDK key, so an app cannot stream telemetry into it. The 150 signup credits belong to the Parsaa app’s chat, not to Orbit’s AI actions.

​
Free versus paid, in one line each

  • Free forever, on every tier: uploading and storing evidence, every read in the console, Insights, the Analytics tabs your plan carries, syncing agent runs and screen maps from the Parsaa app, and the whole telemetry pipeline.
  • Costs credits, always with an estimate first: a pull request review, a crash diagnosis, an Instruments trace analysis, a store review theming, an AI memory merge, and Ask analytics.

​
What Orbit never does

Orbit is read only outward. It never writes to App Store Connect, never writes to your app, and the one thing that ever writes to your repository is Apply suggestion on a review finding, which a person clicks. Everything else it writes is its own state: a crash group’s status, an alert rule, a project setting, a review decision posted back as a GitHub check run or a comment.

​
Where to start

1

Create a project

Sign in at platform.parsaa.app with your Parsaa account and create a project for the app.
2

Add the SDK

Add the Swift package and start it with the project’s SDK key. See SDK installation.
3

Choose what it may collect

Settings, Telemetry is the capture policy: eight surfaces, each with a switch and a share of sessions. See Capture policy.
4

Wire the CLI into CI

orbit upload sends .xcresult bundles, build logs, dSYMs and traces. See The orbit CLI.

What the SDK collects

What is automatic, what your app has to call, and what never leaves the device.

The console

A paragraph per page, from Overview to Settings.

Analytics

Identities, lifecycle states, revenue and the weekly digest.

MCP and agents

Connect Claude Code, Cursor or Codex to a project.