A download of the Orbit source code through the authorized sales channel: the Next.js application, components, Server Actions, PostgreSQL/Drizzle schema, seed script, configuration files, documentation, CHANGELOG, and commercial license. It is a downloadable self-hosted codebase — not a hosted account or repository invitation.

No. Orbit is a self-hosted codebase that you deploy and operate yourself. You can use a platform such as Vercel or your own infrastructure, with PostgreSQL for the database. Orbit does not require a separate Orbit-hosted runtime.

Orbit itself is sold as a one-time source-code purchase. The pricing shown inside the application is different: it demonstrates the SaaS billing system included in the boilerplate. Those application plans are Solo at $0/month, Team at $19/month, and Studio at $49/month, with monthly Stripe subscriptions for the paid tiers. These are example SaaS plans, not Orbit purchase tiers.

Yes, subject to the applicable commercial license and sales-channel terms. The license is intended to let you modify Orbit and use it as the foundation for your own End-Products. You may sell those End-Products, but you may not redistribute or resell the Orbit source code itself. Marketplace terms may impose additional restrictions.

Yes, within the scope of the applicable commercial license. The standard Orbit license permits unlimited End-Products owned by the Licensee. Always check the exact license and sales-channel terms that apply to your purchase.

No. The commercial license does not permit redistribution, resale, sublicensing, or republishing the Orbit source as a template, starter, boilerplate, UI kit, or open-source project. You can sell the products you build with Orbit, not Orbit itself.

No. The buyer release is intended to be a clean reusable boilerplate. Marketplace-specific sales configuration, private credentials, and seller routing are kept separate from the buyer product codebase.

Yes. The included billing flow is built around monthly SaaS subscriptions: Solo is free, while Team and Studio use recurring monthly Stripe Prices. Stripe configuration is provided through environment variables, so you connect your own Stripe account and products when deploying your application.

Features that depend on external services require their corresponding credentials. For example, real GitHub or Google OAuth requires the provider client ID and secret, and paid Stripe subscriptions require the appropriate monthly Stripe Price IDs. The codebase does not silently substitute fake provider identities or fake payments for missing production credentials.

The standard Orbit license includes one year of updates for the applicable major version. The code you already received remains licensed to you after the update period ends. Update delivery and availability follow the applicable authorized sales channel and license terms.