Security & trust

Access control you can point to.

Where your data lives, who can see it, and what happens on a lapsed plan — in plain terms, not a compliance PDF.

Your metal, your keys — Enterprise

Enterprise runs a signed Docker image on infrastructure you own. Labs sends a license key and a pull token — never source, never a git clone, never our payment or model-provider keys.

Domain-locked workspaces

A company email is required to create a workspace — personal inboxes are blocked at signup. Studio and Enterprise also lock invites to your @company domain, so a workspace can't quietly pick up outside members.

Bring your own model key

The copilot uses a Labs-hosted model by default. From Studio up, point it at your own OpenAI-compatible endpoint with your own key — prompts and responses never have to leave infrastructure you control.

Agents stay in the sandbox

The agent crew deploys only to staging and sandboxes — for Salesforce the runner checks the org and refuses production; for other stacks agents can run only the build, test and staging-deploy commands you configure, through a locked wrapper on your own machine; passwords and tokens never reach Pravadh PM. Only the super admin can set agents up or issue runner tokens.

Nothing merges without a person

With Git connected, each story works on its own branch and the Dev Agent opens a pull request. The agents have no git commands of their own and refuse to work on main or your base branch — review and merge stay with your team.

Roles, guests, and permission sets

Owner, admin, member, and guest are enforced server-side, not just hidden in the UI, with Salesforce-style permission sets on top. The person who owns a story governs what the agents do on it. Guests can look without consuming a paid seat or getting write access to costs and settings.

An activity feed, not a black box

Comments, status moves, assignments, and budget changes log to the org's activity feed with who did it and when — visible from Command Center, not buried in a database only Labs can query.

Lapse locks, it doesn't wipe

When a subscription lapses, people can still read — they can't create or edit. Owners and admins get an email every two days until it's resolved. Nothing is deleted for non-payment.

Ask Labs for what your plan doesn't publish here

Some questions — data residency for a specific region, a signed DPA, a security questionnaire — depend on plan and deployment. Enterprise buyers running self-hosted get the most direct answers since Labs never touches the running data at all.