Security
Three commitments, 14 practices we can name, and a clear list of things CoBuilder does not claim today.
i / Commitments
Everything else on this page exists in service of these three.
billing control
Credits are prepaid. CoBuilder checks your remaining balance before AI work and external compute work. When balance reaches zero, autonomous work pauses at the next safe checkpoint and waits for you.
data isolation
Multi-tenant data is protected with Postgres row-level security policies using read and write checks. The storage layer enforces account boundaries instead of relying only on application code.
data ownership
Files live in a per-organization Git repository on CoBuilder servers for history, diff, and revert. The desktop app syncs a local mirror to ~/CoBuilder/{your-email}/ so you always have an exportable copy.
ii / Practices
Specific mechanisms, grouped by the part of the product they protect.
The backend checks available credits before AI work and external compute work. CoBuilder does not run a metered overage path.
Payment details are collected by Stripe. CoBuilder servers and databases do not store raw card numbers or CVC values.
Postgres row-level security policies protect multi-tenant data with storage-layer read and write checks.
Every managed file write is stored as history in a server-side Git repository, which is why CoBuilder can show diffs and revert earlier file states.
File bytes in Google Cloud Storage and metadata in Neon Postgres are encrypted at rest with provider-managed AES-256 encryption.
Third-party credentials are held server-side with Google Cloud Secret Manager controls. User-supplied connector credentials are encrypted with AES-256-GCM before database write.
The desktop app runs with context isolation on, sandbox on, and Node integration off in the renderer. Filesystem operations are checked for path traversal before disk access.
Backend endpoints validate inputs with Zod schemas before malformed input reaches application logic, the database, or downstream providers.
The published limits are 10 authentication requests per minute per IP, 30 AI calls per minute per user, and 300 general API requests per minute per user.
The desktop app does not hold AI provider keys. Model calls route through the CoBuilder backend, with provider credentials managed in Google Cloud Secret Manager.
Sign-ins, sign-in failures, billing changes, credential changes, and organization permission changes are written to structured application logs for security investigation.
Server error reports strip request bodies and authorization or cookie headers. Desktop error reports strip email, name, and IP before leaving the app.
Traffic uses TLS 1.2 minimum, with TLS 1.3 negotiated when both client and server support it.
CoBuilder uses frontier AI models from major providers and can route work based on task fit and provider availability.
iii / Data flow
CoBuilder is cloud-first. The server-side repository is the source of truth, and the desktop app keeps an exportable local mirror on your machine.
Local CoBuilder desktop app with a synced local mirror at ~/CoBuilder/{your-email}/.
Server-side source of truth: per-organization Git repository, file bytes in Google Cloud Storage, metadata in Neon Postgres.
A frontier model receives only the context needed for a specific request.
iv / Honesty
CoBuilder names what is true today and leaves future hardening off the page until it is real.
Not today. CoBuilder will only publish a badge when an external auditor has signed off.
CoBuilder is built for individual professionals. It is not currently positioned for regulated-data customers.
Not offered in v1. CoBuilder relies on its backend and hosted AI providers.
Not yet. Providers may retain inputs and outputs for up to 30 days for abuse monitoring and safety review under standard commercial terms.
v / Disclosure
Send the report to security@cobuilder.me with impact, reproduction steps, and whether anyone else has been told.
14 days free. 30,000 credits to start. Cancel anytime.
