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 privately maintained Next.js application.
| Decision | Amsonia Next | Amsonia Platform |
|---|---|---|
| Primary stack | Next.js 16 full-stack application | Go API + Next.js product and operations surfaces |
| Tenancy model | Single-tenant by design | Multi-tenant, with tenant and workspace-aware boundaries |
| Distribution | Private source; contact for availability | Commercial source-code package |
| License | Terms confirmed with Willuny Labs | Commercial source license |
| Billing | Stripe checkout, subscriptions, and webhooks | Stripe-oriented commerce, billing, invoice, and fulfillment surfaces |
| Best fit | Founders shipping a focused product from one Next.js codebase | B2B products that require organizations, delegated access, Go, and broader operations |
| Operating surface | One application runtime plus PostgreSQL and configured providers | Separate frontend, API, database, and product operations |
Recommendation
Start with the application your product needs.
Start with Next when its single-tenant model is sufficient. Choose Platform when multi-tenancy and Go are requirements, not speculative future possibilities.