User-scoped identity
Firebase Authentication establishes the user identity used by both the app and API authorization layer.
Security model
Boundaries before autonomy.
DoneOS is designed so mobile clients, AI agents, integrations, and persistent data do not share one unrestricted trust surface.
Access follows the actor.
Every command is authenticated, authorized, validated, and attributable before state changes.
Hashed agent keys
Agent credentials are shown once, stored as one-way hashes, scoped to an owner, and revocable.
Encrypted integrations
Slack access tokens remain server-side and are encrypted before persistence.
User-scoped records
Goals, work, actors, events, runs, zones, and integrations live under an explicit user boundary.
Write path
Agents never receive database credentials.
MCP translates typed tools into API commands. The service verifies the actor and applies state transitions with their execution events.
- Flutter or MCP client
- DoneOS API
- Firestore
Current posture
Private beta, stated plainly.
DoneOS has application-level controls and local verification, but it does not currently claim SOC 2, ISO 27001, HIPAA, or independent audit certification.
- Authentication and ownership enforcement
- Revocable scoped agent access
- Idempotent, attributable state transitions
- No active hosted GitHub workflows
Private beta
Start with bounded execution.
Use DoneOS where agent scope, recoverability, and visible accountability matter.