Security
Powerful agents, on a short leash.
Orbit can act in your apps — so it's designed to ask, to show you what it will do, and to keep your credentials out of reach of the model.
OAuth for every app
Apps are connected with official OAuth sign-in. You can disconnect any app, any time.
Credentials stay out of the prompt
Tokens are held by the integration layer, never pasted into chat or shown to the model.
Approval before actions
In chat, sending, posting and deleting wait for your confirmation. Routines run only after you review and save them.
Isolated cloud browser
Web tasks run in a separate cloud desktop per agent, streamed to you behind authentication.
In place today
What Orbit does now.
- Sign in with Google or GitHub — Orbit stores no passwords
- Workspace pages require a signed-in session
- Apps connected through OAuth; disconnect any app per agent
- App tokens are held by the integration layer, not shown to the model
- Chat actions that send, post or delete need your explicit approval
- Routines run only after you review and save them, and can be paused or deleted
- Each agent's cloud browser runs in its own sandbox; the live stream requires authentication
Planned
- Audit log export soon
- Team roles and permissions soon
- Data retention controls soon
- Published privacy policy and terms soon
Chat · Sales assistant
agent:sales-rep
Email the new pricing to the three clients from today's call and tell the team.
Confirm external action
nothing has been sent yet
- Send “Q3 pricing update” to 3 clients
- Post the summary in #sales
- Mark 3 rows as ‘contacted’ in Leads — Q3