Everything you need to know about BaselineNext.
BaselineNext is built on reusable platform capabilities such as account authentication, users, billing, admin, email, Redis, jobs, observability, and governance.
No. It is intended to be cloned into future products, then extended with project-specific domain modules, branding, copy, data model additions, and policies.
Set APP_ID and NEXT_PUBLIC_APP_NAME, replace logo assets, configure email and Stripe, update pricing/product copy, then add project-specific governance in governance/project.md.
An account is the tenant root and billing owner. Users belong to accounts and represent application users that can be enabled, disabled, invited, or managed by the account.
Yes. The starter includes reusable Stripe checkout, portal, subscription state, invoice snapshot, pricing configuration, and webhook handling foundations.
Pricing is exposed through the reusable billing catalog and rendered on the pricing page. Downstream projects should replace the placeholder catalog records with product-specific plans.
The default trial is 7 days. Trial limits can be adjusted through billing and platform configuration for downstream projects.
The baseline keeps admin account lookup, user management, billing views, invoice snapshots, support requests, audit events, scheduled jobs, platform settings, incidents, and observability surfaces.
Redis and cache keys use the configured APP_ID and central key builders. Feature code should not hand-concatenate Redis keys.
Use governance/project.md for downstream product rules, domain vocabulary, approved exceptions, operational anchors, and project-specific test notes.