Straight answers to fair questions.

Clear answers on agents, systems, pricing, credits, controls, setup, security, and support.

Need product help? Include your workspace email and a run link.

go.orbitdashboard.co

Questions

A
Popular answers
What does Orbit do?
Agents, systems, approvals, and results in one workspace
Open
How do credits work?
One pool shared across your plan
Open
Where does approval happen?
Consequential actions wait in one queue
Open
Clear
Product answers
Human
Support path

About Orbit.

Four answers about the product and dashboard.

Orbit gives you seven business systems and 43 specialist agents in one dashboard. Connect your accounts, assign work, set approval rules, and follow every result from the same workspace.

Orbit is self-serve software. You choose systems, connect accounts, and run agents month to month. Enterprise support is available for larger rollouts and custom requirements.

Orbit's product and engineering team builds and maintains the systems, agent instructions, integrations, controls, and evaluation checks.

It is the shared control room for agents, systems, workflows, approvals, connections, credits, run history, and results.

AI concepts, plainly.

Six answers without the jargon.

A regular automation follows fixed steps. An agent can interpret context, choose among allowed actions, and ask for approval when a decision crosses the boundary you set.

Automation handles predictable rules. AI handles language and judgment. Orbit combines both so sensitive boundaries stay deterministic while flexible work can adapt.

It splits a larger job among focused specialists, then combines their work. It helps when research, drafting, review, and action need different context or checks.

Retrieval-augmented generation gives an agent relevant excerpts from your approved knowledge before it drafts an answer. Orbit uses it when current business context matters.

It is the information a model can consider during one task. Sending only useful context keeps work focused and avoids spending credits on irrelevant text.

Orbit chooses models by task quality, safety, latency, and cost. The provider is part of the system design, not something an agent changes on its own.

Ethics and boundaries.

Seven answers about responsible agent work.

AI should remove repetitive work while keeping people in control of judgment, risk, and customer relationships.

Orbit does not choose a model for branding. Each system uses a provider and configuration selected for the task's quality, safety, cost, and data requirements.

Orbit is built to remove repetitive tasks and expand team capacity. You decide which work agents own and which decisions remain human.

Orbit does not use customer workspace data to train Orbit models. Provider data terms depend on the service and deployment path; Enterprise customers can document required handling terms during procurement.

No. Orbit does not support fake identities or deceptive impersonation. Customer-facing teams choose clear disclosure rules and keep human review on sensitive conversations.

Orbit does not support spam, deceptive impersonation, unauthorized data collection, deepfakes, or offensive cybersecurity work.

Safety is enforced through allowed actions, scoped credentials, tenant isolation, role controls, approvals, run history, and a kill switch. Higher-risk work keeps tighter boundaries.

Global operations.

Six answers about regions, languages, and data requirements.

Orbit is operated from the United States and serves customers online. Product access is self-serve; support and Enterprise requirements are handled directly with the Orbit team.

Orbit hires for product judgment and engineering depth. Team location does not change which systems or agents a customer can use.

Standard support is handled during published business hours. Enterprise response and escalation requirements are documented during procurement.

Agents can draft and classify work in multiple languages. Customer-facing content should be reviewed by a fluent operator before higher autonomy is enabled.

Share residency and regulatory requirements before connecting data. Available regions, providers, retention, and deployment options are scoped to the plan and workload.

Yes, subject to billing, legal, provider, and data-handling requirements for the customer's location.

How Orbit works.

Five answers about setup, controls, and day-to-day use.

Choose a plan, create your account, connect the accounts your first workflow needs, and assign an agent. Guided setup walks through the first run.

Setup time depends on the accounts and business context your chosen systems need. Regulated intelligence and security work also requires workspace or asset verification.

No. Plans, connections, agents, workflows, approvals, and run history are managed through the dashboard.

The run records the failure and keeps its context. You can stop, retry, or redirect the work, then send the run link to support if the cause needs investigation.

Yes. Add or remove systems as your operating needs change. They share the same dashboard, controls, connections, and credit pool.

Pricing and plans.

Three answers about subscriptions, credits, and Enterprise.

The platform starts at $59 a month, then you add the systems you want. The full suite is capped at $599 a month or $479 effective monthly on annual billing. It includes 6,000 monthly credits.

Every plan includes the dashboard, Assistant, shared credit pool, all 43 agents, autonomy controls, approvals, run history, kill switch, product updates, and support. Each added system contributes monthly credits.

Enterprise can cover custom workflows, integrations, controls, support, and deployment requirements. Contact Orbit with the job and constraints to scope the right approach.

Security and data.

Four answers about storage, providers, regulated workloads, and logs.

Orbit uses managed cloud infrastructure with encryption in transit and at rest, tenant isolation, role controls, and a credential vault. Enterprise residency or deployment requirements are scoped before onboarding.

Orbit does not use customer workspace data to train Orbit models. Provider handling terms depend on the service and deployment path.

Regulated workloads require review before data is connected. Orbit scopes the data path, provider terms, access rules, retention, and required agreements for the specific workload.

Yes. Run history records the actor, system, connected account, approval, status, cost, and result. Access and retention follow workspace policy and plan configuration.

See Orbit in your own workspace.

Start a 7-day trial, connect the accounts your first workflow needs, and keep approval under your control.