Organization boundary
Every organization-scoped read and write is protected by database row-level security or a server operation that checks the authenticated member and role.
Security / Access architecture
Your procedures are operating data.
Rampwise separates identity, organization membership, draft visibility, learner access, and billing state into distinct authorization decisions.
Draft boundary
Owners and admins can preview drafts. Learners require a published course, an assignment, and active organization access before lesson bodies are retrievable.
Secret boundary
SOP generation writes use a server-only Supabase credential. Model, database, and billing credentials are never shipped to the browser.
Billing boundary
When checkout is activated, Stripe webhook bodies are verified against the endpoint signing secret and event identifiers make subscription updates replay-safe.
AI provider boundary
Generation happens server-side.
Submitted source text and generation instructions are sent to the configured model provider to create the course. Rampwise currently supports OpenRouter with a direct Anthropic fallback. Submit only information you are authorized to process through those providers.
Payment boundary
Raw card details stay with Stripe.
Paid checkout will use hosted Stripe sessions. Rampwise stores only the customer, subscription, price, status, and renewal identifiers needed to enforce access. It does not collect raw card numbers.
Current boundary
Precision over posture.
Rampwise does not claim SOC 2, HIPAA, ISO 27001, or regulated-data eligibility at launch.
Course deletion, formal export tooling, configurable retention, and enterprise provider agreements are not yet self-serve features.
Security reports and procurement questions can be submitted through the private Trust Center intake.
Submit a private request