Platform or Next? Choose by architecture.
Both products keep source ownership explicit. Platform adds a Go service and multi-tenant operating model; Next keeps the system inside one open-source Next.js application.
| Decision | Amsonia Platform | Amsonia Next |
|---|---|---|
| Primary stack | Go API + Next.js product and operations surfaces | Next.js 16 full-stack application |
| Tenancy model | Multi-tenant, with tenant and workspace-aware boundaries | Single-tenant by design |
| Distribution | Commercial source-code package | Open-source Git repository |
| License | Commercial source license | MIT |
| Billing | Stripe-oriented commerce, billing, invoice, and fulfillment surfaces | Stripe and Lemon Squeezy provider adapters |
| Best fit | B2B products that require organizations, delegated access, Go, and broader operations | Founders shipping a focused product from one Next.js codebase |
| Operating surface | Separate frontend, API, database, and product operations | One application runtime plus PostgreSQL and configured providers |
Recommendation
Prefer the smaller truthful boundary.
Start with Next when its single-tenant model is sufficient. Choose Platform when multi-tenancy and Go are requirements, not speculative future possibilities.