Bring the team into one place. Keep the Workspace useful before and after DOSS activation.
DOSS Cloud + Remoco + DOSSBOT
The cloud agents call home.
Any harness. Any model. Any context. Your keys. Your cloud.
One control plane for workstations, worktrees, databases, and compute.
New accounts, applied to first-month usage.
Any harness
One control plane
Your cloud
One shared surface
The work starts before kickoff.
Prospects and customers enter the same governed Workspace your team uses to deliver. Conversations, Apps, files, sessions, and automations carry forward.
Useful from the first month
Know what the monthly spend buys.
Pick the job. Each reference workload ties one monthly estimate to the useful work it keeps moving.
For light, bursty work
Keep one agent-ready Workspace available.
Forty workstation hours plus a Lite model budget for the jobs that should not wait on a laptop.
1 standard Box · 40 hours · Lite tokensFor continuous supervision
Give CI an agent that stays on the job.
One persistent supervisor with durable retries, full-month compute, and a balanced model budget.
1 standard Box · 720 hours · Balanced tokensFor parallel implementation
Give one engineer a large cloud workstation.
Parallel worktrees, shared cache, and a balanced model budget without rebuilding local environments.
1 large Box · 160 hours · Balanced tokensOne continuous steel thread
From first conversation to live operation.
The Workspace stays general purpose. Discovery, implementation, L2L, pre-sales, and support arrive as installable Apps, not separate Box types.
Start together
Provision one Organization, one shared Workspace, and one primary Box. Add collaborators with explicit observe or steer access.
ni/mo:inInstall the process
Pin presentation or headless Apps for the work at hand. Keep chat, files, terminal, models, skills, and connectors available underneath.
ni/mo:in + ni/mo:outActivate without migration
Bind the same Remoco Workspace to DOSS Cloud when the customer is ready. Identity, context, and collaboration continue in place.
ni/mo:outEngagement that keeps moving
Automations turn the Workspace into a participant.
Create from a template or plain prompt. Trigger on a schedule, signed webhook, or Workspace event. Every run keeps its session, outcome, duration, and spend visible.
- Governed agent runs, not detached scripts
- Approval modes and hard spend ceilings
- Useful output plus failure notification
Governed by default
Shared does not mean unbounded.
DOSS Cloud separates identity, transport, runtime, and support authority. The Box gets only the short-lived grant needed for the current operation.
WorkOS identity
Browser sessions and CLI authorization bind to the exact Organization and current membership.
Exact Box grants
Observe and steer are checked per action. Control-plane management never becomes Box authority.
Budgets and approvals
Model spend, effect ceilings, run approvals, and support access stay visible and revocable.
Console truth
Inspect agents, sessions, worktrees, services, versions, health, and spend from one read-only surface.
Supervised alpha
Start the work in your DOSS Cloud Workspace.
Bring any harness and model. Keep the context, keys, and cloud under one governed Workspace.