Server-owned organization context
The signed-in membership determines the active organization on the server. A browser-supplied organization ID is never treated as authorization.
Private beta · An operating workspace for founders and business owners.
Security and trust
Venturoost is built around tenant isolation, server-side authorization, evidence, and explicit approval. It is still a private beta, so this page also names what has not yet been certified.
Security model
The product does not depend on hidden buttons or client-side state to protect business data. Server-owned organization context resolves access, and Postgres row-level security reinforces that boundary in the database.
Implemented controls
The signed-in membership determines the active organization on the server. A browser-supplied organization ID is never treated as authorization.
Tenant-owned Postgres tables use row-level security, explicit organization filters, and same-tenant relationship checks.
Owner, administrator, manager, and employee permissions are checked at the mutation boundary. Sensitive team and connector operations remain restricted.
Findings, proposals, approvals, work completion, and internal execution artifacts retain source references, immutable receipts, or audit events.
High-impact actions require a fresh, single-case approval bound to the exact proposal and evidence. Standing approval is forbidden.
The current product cannot change accounting, banking, payroll, HR, device, or other external provider records.
Generated suggestions
Some suggestions are generated with AI. Every one links to its evidence, and nothing happens without your approval.
Current limitations
Questions
The FAQ explains data sources, integrations, pricing, support, and what the private beta can do today.