Confiança e segurança
Ferramentas de segurança criadas para quem entrega
Entregue mais rápido, com os controles que sua equipe e seus clientes esperam.
Find it before your customers do
Every Vibely app is scanned as it’s built. See how Vibely scans your app
Scanned as you build
Every publish kicks off a background scan of your application code and any exposed PII. A deep scan, which you start on demand, adds your RLS policies, database schema and dependencies — five scanners in all.
Ranked by severity
Findings land in the project Security view ordered by how much they matter, each one naming the file and the rule it broke, so you can tell a real hole from a style note.
Fixed before you ship
Safe dependency fixes can be applied for you, and a workspace can block publishing outright while a critical finding or exposed PII is outstanding.
Every vendor that touches your data is listed.
Cloud hosting, sandboxes, AI inference, payments, email and observability — named, with the country each one runs in.
- Uptime commitment (/sla)
- 99.5%
- In transit and at rest
- Encrypted
- Sandbox isolation
- Per-project
- Vibely trains models on your data
- Never
Os controles que sua equipe de segurança espera
Aplique SSO e acesso por função, mantenha a publicação atrás de permissões separadas e saiba que a própria Vibely nunca treina modelos com seu código ou seus prompts.
Access and control
SAML or OIDC single sign-on with optional SCIM provisioning on Business workspaces. Owner, Admin, Editor and Viewer roles are evaluated server-side on every request — viewing, editing, publishing and publishing publicly are separate permissions.Guardrails for building & publishing
Editing, publishing and publishing publicly are separate permissions, and every project carries its own visibility — public, private, workspace, or named member groups. Teams move fast without exposing in-progress work.Secrets handled securely
Encrypted at rest, scoped to your workspace, and never returned in plaintext. Rotate or revoke one and every running sandbox picks up the change immediately — no redeploy.Where your data runs
Application servers run on Google Cloud in the United States (us-east1) and project sandboxes on E2B in the United States; files are stored in Cloudflare R2; the database and authentication run on Supabase in Singapore. Every subprocessor and its location is listed in Annex 3 of our DPA at /dpa. There is no region selector yet.See subprocessorsVibely does not train on your data
Vibely does not use your prompts, code, or project data to train models. The model that serves a request processes it under its provider's own terms: the default, DeepSeek, is an open-weight model we run on US-hosted inference providers (named in Annex 3 of our DPA), never on DeepSeek's own servers; OpenAI, Anthropic, Google and Fireworks exclude API traffic from training. Product-improvement data collection is off by default; a workspace can opt in from Privacy & security settings.Isolation by design
Strict logical separation between workspaces and projects with row-level security on shared databases. Boundaries are explicit before publishing.Continuous monitoring
Rate limiting and abuse detection on the agent loop, applied at the IP, user and workspace level. Runtime errors and anomalies surface in our observability stack and we review what it flags.Automatic security scanning
Scanners check your RLS policies, database schema, application code, dependencies and exposed PII. Findings are ranked by severity in the project Security view before you publish.Security scansProtected infrastructure
Every build runs in its own cloud sandbox with its own filesystem, behind an edge CDN on every route. Vibely never enters your environment and needs no inbound connection from your network.
Criado para a forma como você entrega
Evidence you can hand over
Export your scan findings as a report for a customer security review or investor diligence. It is a scan result, not a SOC 2 or ISO 27001 audit — but it shows exactly what was checked and what you fixed.
Security answers for founders
Ask us what we can evidence today — how builds are isolated, which subprocessors touch your data, and what we hold and do not hold on the compliance side. We hold no SOC 2 report and no ISO 27001 certificate. We answer in writing.
Find vulnerabilities before they find you
Five scanners check your RLS policies, database schema, application code, dependencies and exposed PII on a deep scan you run on demand; every publish additionally kicks off a background code and PII scan. Business workspaces can schedule recurring deep scans, and the safe dependency fixes can be applied for you.
Frameworks que suportamos
- SOC 2Not held
We do not hold a SOC 2 report and no audit is under way. We will say so here on the day we engage an auditor, rather than before.
- GDPREU data protection
Article 28 Data Processing Agreement published at /dpa, including the EU SCCs and the UK Addendum. It applies without signature.
- ISO 27001Not held
We do not hold an ISO 27001 certificate and no certification process is under way. What we run is described on this page; none of it is externally attested.
Found a vulnerability in Vibely itself? Read the responsible disclosure policy or the Data Processing Agreement. Current availability and past incidents are on the status page.
Trust center
How long we keep your data, the documents a security review asks for, and how to reach us. Vibely never trains AI models on your content.
Data retention
| Chats, files and apps | Until you delete them. Enterprise admins can set chats and files to be deleted after 30 days to 2 years. |
|---|---|
| Deleted account | 30 days (sign in to cancel), then everything is deleted |
| Deleted workspace | 60 days, restorable by its owners, then deleted |
| Data export you asked for | 7 days |
| Audit logs | 1 year |
| Contact and sales requests | 2 years |
| Error reports | 90 days |
| Database backups | 7 days after deletion, then gone |
| Invoices | As tax law requires, with our merchant of record |
Request security documents
For a vendor review: we send what we have, some under NDA.
FAQs
Pronto para construir com confiança?
Cada provedor de modelos processa suas solicitações sob os próprios termos. O modelo de build padrão, DeepSeek (escolhido pelo Auto), é de pesos abertos: nós o executamos em provedores de inferência hospedados nos Estados Unidos, nunca nos servidores da própria DeepSeek. O Anexo 3 do nosso DPA nomeia cada um.