Security
How we protect your store
Sevra hosts your brain as plain markdown files. This page says exactly what protects those files today. Sevra is in early access, and we describe what exists, not a roadmap.
Last updated: August 16, 2026. This page describes the current Sevra product and is periodically reviewed and updated.
Architecture
Two separate planes
Account and billing data live in the application. Your store contents live in object storage. Your own AI agent normally runs outside both. When you explicitly authorize a Sevra-run function or run, Sevra executes only the declared work under that grant.
Sevra platform
Application and account
- Authentication (WorkOS)
- Billing (Stripe)
- Application data (Neon Postgres)
- Application hosting (Vercel)
- Transactional email (Resend)
Your store
Your data, in the open format
- Plain markdown files
- The open db.md format (Apache-2.0)
- Object storage (Cloudflare R2)
- Separate encrypted recovery backups
- Full export at any time
- Deletion on request
- Self-hostable, always
Encryption
Encrypted in transit and at rest
In transit
All connections use TLS: your browser to Sevra, Sevra to its providers, and every read and write to your hosted store.
Store contents at rest
Store contents live in Cloudflare R2 and are encrypted at rest by the storage provider. Every committed mutation also writes an application-encrypted recovery envelope to a separate R2 bucket.
Recovery backups
Recovery objects are protected from deletion or overwrite by a 30-day bucket lock. Each brain has a separate data key. An explicit brain or account deletion destroys that key immediately, making retained backup ciphertext unreadable while the storage lock expires.
Application data at rest
Account and application data live in Neon Postgres, which encrypts data at rest.
Payment data
Payments are processed by Stripe. Card details go to Stripe directly and never touch Sevra's servers.
Authentication
Managed sign-in, no passwords held
Sign-in
WorkOS AuthKit handles sign-in. Supports email, Google, and enterprise SSO providers. Sevra does not store passwords.
Sessions
Sessions are managed through WorkOS AuthKit and checked on every request to the application.
Brain vault
You may choose to store credentials in a brain-scoped vault. Values are encrypted with a separate key hierarchy. The web dashboard shows names, consumers, and audit events, never secret values. Owner readback is authenticated and limited to the CLI. Functions and runs receive only the values they declare.
Practices
How we run the platform
Secret hygiene
Production credentials live in the deployment platform's encrypted environment store, not in code. The most sensitive values are write-only: readable by the running application, not by people browsing a dashboard.
Private code, open format
The platform codebase is a private repository with access limited to the team. The db.md format itself is the opposite: public, Apache-2.0, and designed to be readable without us.
Managed providers
Authentication, billing, hosting, database, and email run on established managed providers rather than systems we build and patch ourselves. Fewer custom systems means fewer places to get security wrong.
Infrastructure
Where things run
Application
The Sevra application runs on Vercel, hosted in the United States.
Application data
Account and application data live in Neon Postgres. Store contents do not live in this database.
Store contents
Hosted stores and their separately encrypted recovery backups live in isolated Cloudflare R2 buckets with distinct runtime credentials.
No customer machines
Sevra runs no customer VMs or dedicated machines. Your own agent uses your own AI account. Credentials enter Sevra only when you deliberately put them in the brain vault for an authorized consumer.
Status
Where security stands
Sevra is in early access. A formal third-party security audit has not yet been performed, and we do not claim certifications we do not hold. Here is the plain state of things.
In place today
TLS on every connection. Encryption at rest through the storage providers. Separately encrypted, retention-locked recovery backups. WorkOS-managed sign-in. Stripe-handled payments. Brain-scoped vault encryption and consumer isolation.
Not done yet
No formal third-party security audit has been performed. We hold no SOC 2 report and no penetration test on file. When that changes, this page will say so.
Not collected by default
Card details go directly to Stripe and passwords are handled by WorkOS. Your own agent's credentials stay outside Sevra unless you deliberately save a credential in the brain vault.
Ownership is a security property
Your store is plain files in an open format. You can export everything at any time and host it anywhere. Whatever happens to Sevra, your data stays readable.
Deletion
Delete your brain or account and Sevra removes the active copy, vault values, and the per-brain recovery key. Retention-locked backup ciphertext becomes unreadable immediately and is physically pruned after its lock expires. Deletion on request is always available: privacy@sevrahq.com.
We would rather understate this page than decorate it. Formal review comes as the product matures. Until then, this page states what exists.
Data processing
Sevra is operated by VibeCraft Inc. We act as a data controller for account and billing data, and we process your store contents on your behalf in order to host, index, and organize them.
Sub-processors: WorkOS (authentication), Stripe (billing), Vercel (application hosting), Neon (application database), Cloudflare (object storage and isolated functions), and Resend (transactional email). Anthropic processes selected content only when you authorize an available Sevra-run AI feature.
A data processing agreement is available on request: legal@sevrahq.com.
Incident response
If a security incident affects your account or your store, we notify affected customers without undue delay after confirming and assessing it. Incidents are documented and reviewed.
Contact
Security questions and responsible disclosure: security@sevrahq.com. If you find a vulnerability, tell us there first. We read and answer every report.
See also: Privacy policy · Terms of service