Security Is Part of the Product.
Venus is designed with secure authentication, controlled access and server-side protection in mind.
Our Commitment to Technical Honesty
We do not make unrealistic promises like 'impossible to hack' or '100% secure'. Our posture relies on defense-in-depth, strict tenant scoping, PostgreSQL RLS, and keeping sensitive secrets strictly server-side.
Mediated Architecture Between Browser & Business Systems
Browsers never directly interface with core ERPNext databases or internal service networks. All actions pass through authenticated, scoped server boundaries.
Controlled Data Flow from Browser to Business Systems
A multi-layered architecture where clients never directly query core business engines. Requests are verified and scoped server-side.
Venus Server
Server-Side Scope GateServer runtime validates workspace membership and enforces request authorization. API secrets and service-role keys remain exclusively on server.
Scoped Authorization & Tenant Isolation
Every data access is anchored to an authenticated user's verified workspace_id, enforced via PostgreSQL Row Level Security (RLS) to prevent cross-tenant leakage.
Tenant Isolation Pipeline
Enforced VerificationTechnical Safeguards & Operational Controls
Here we outline the transparent implementation state of each security domain, allowing your engineering and security teams to review our actual posture.
Authentication & Identity Management
All client accounts are gated through Supabase Auth, utilizing modern salted hashing algorithms (bcrypt/Argon2) and short-lived signed JWT session tokens.
Technical Implementation Details:
- Invite-only onboarding: No public unverified signups to sensitive client portal spaces.
- Cryptographically signed JWT verification on all protected server functions.
- Multi-factor authentication (MFA) can be enabled where supported by the identity provider and enterprise deployment configuration.
Role-Based Access Control (RBAC)
Strict separation between studio engineers, administrators, and client workspace members. Access policies are verified server-side on every transaction.
Technical Implementation Details:
- Clients can never view studio-internal administration desks, internal team notes, or other clients' spaces.
- First signup receives administrative claim; subsequent accounts require explicit workspace invitations.
- Granular workspace membership mapping enforced through database relation constraints.
Tenant Data Isolation & PostgreSQL RLS
Every portal table carries a mandatory `workspace_id` foreign key. PostgreSQL Row Level Security (RLS) policies evaluate `is_workspace_member()` on every query.
Technical Implementation Details:
- Database engine strictly drops attempts to query or mutate rows outside authorized workspace membership.
- Storage bucket isolation: Files reside in `portal-files/<workspace_id>/...` checked by storage security policies.
- Short-lived signed download tokens (60-second TTL) eliminate permanent public URLs for sensitive documents.
Secrets Stay Server-Side
High-privilege credentials, Stripe secret keys, ERPNext API tokens, and AI provider secrets are never shipped to client JavaScript bundles.
Technical Implementation Details:
- Client browser bundles only receive public publishable keys (`VITE_SUPABASE_ANON_KEY`, `VITE_STRIPE_PUBLISHABLE_KEY`).
- All mutating business functions execute via secure TanStack Start / Nitro server functions.
- Strict environment variable separation between server runtime and client bundle builders.
Encryption in Transit & at Rest
Modern cryptographic cipher suites safeguard data across network transit and persistent database storage volumes.
Technical Implementation Details:
- Enforced TLS 1.3 / 1.2 across all public and internal service communications.
- Persistent volume encryption for managed PostgreSQL and Docker volumes on underlying cloud storage.
- Encrypted backup zip archives transferred to cloud storage destinations.
Automated Snapshots & Disaster Recovery
Dual-engine snapshot pipelines capture PostgreSQL cluster data and ERPNext MariaDB databases to prevent data loss.
Technical Implementation Details:
- Automated dual-engine dump scripts (`scripts/backup-databases.ps1`) capture both PostgreSQL and ERPNext schemas.
- Compressed and timestamped `.zip` archives generated with automated retention cycles.
- Off-site synchronization to independent cloud storage (Google Drive / S3 destinations).
Containerized & Edge Infrastructure
Venus deploys within isolated Docker containers orchestrated behind modern reverse proxies, separating frontend presentation, API gateway, and database tiers.
Technical Implementation Details:
- Isolated container networks prevent cross-service lateral movement.
- Stateless SSR rendering layers prevent in-memory cross-request session leakage.
- Container healthchecks and automatic process restarts ensure high availability without persistent corrupted states.
Audit Logging & Operational Monitoring
System logs record administrative logins, schema alterations, and authentication events with structured metadata.
Technical Implementation Details:
- Structured application logs capture timestamps, IP origin, and request outcome.
- Error boundaries intercept runtime exceptions without exposing stack traces or internal paths to end users.
- Client activity logs track security-relevant settings adjustments within the client portal.
Delegated Payment Security
Cardholder interactions are delegated to Stripe Checkout. No payment card numbers, CVVs, or bank credentials touch VENUS application code.
Technical Implementation Details:
- Zero raw card storage: VENUS does not maintain payment card databases.
- Stripe signature verification on all incoming webhook events prevents forged settlement requests.
- Payment card handling is delegated to the payment provider where applicable.
Incident Response & Remediation Protocol
A documented triage escalation framework ensures timely response, containment, and notification in the event of suspected security anomalies.
Technical Implementation Details:
- Rapid credential revocation and token rotation protocols for affected services.
- Committed client notification within 72 hours of verified security breaches impacting customer data.
- Comprehensive post-incident postmortem published to affected clients detailing root cause and remediations.
Responsible Disclosure & Vulnerability Reporting
We welcome coordinated, responsible disclosure of potential security vulnerabilities from security researchers and clients.
Technical Implementation Details:
- Contact security desk at security@venus.dev with detailed reproduction steps and proof-of-concept logs.
- We commit to acknowledging reports within two (2) business days and prioritizing rapid remediation.
- Safe harbor: We will not pursue legal action against researchers acting in good faith under responsible disclosure guidelines.
Discovered a Potential Vulnerability?
We welcome responsible reports from researchers and clients. We commit to acknowledging receipt within 2 business days and providing safe harbor for good-faith investigations.