Documentation
startupos product documentation.
Understand how startupos is structured, how your founder data is organized, and how each module fits the weekly operating loop.
Product overview
startupos is structured as six tightly-connected modules, plus a settings system. This document explains what each module is for and how they relate.
Data model
All founder data is stored in a Postgres database with row-level security. Every table that contains user data is scoped by user_id and (where relevant) startup_id, enforced by RLS policies.
Authentication
startupos uses email + password authentication. App routes are protected and unauthenticated visitors are redirected to /login.
Privacy controls
Founder data is owned by the founder. Row-level security ensures workspace isolation, and every account has explicit controls over email, consent, and cookies.
AI in the product
AI features in startupos work alongside founder judgment, grounded in your real workspace context.
Email and consent
Marketing consent is explicit. Signing up or contacting support never auto-subscribes a user to marketing email. Transactional and marketing emails are kept strictly separate.
Roadmap status
A single source of truth for the production-readiness of every startupos feature. We use a small set of explicit status labels instead of vague 'beta' or 'soon' language.