Pay for a plan, or buy the code and stop paying

The complete source code of DailyTM v2 — the Next.js application, the Prisma schema and its committed migrations, every service and its authorization tests, the CI workflow, the seed script, and the documentation. You run it on your own infrastructure and it is yours to modify, rebrand, and deploy as many times as you like within your organization.

No. Billing is optional and off by default. With no POLAR_ACCESS_TOKEN set, the plugin is never registered, the billing interface is absent, every organization is SELF_HOSTED, and every limit is unlimited. You would only configure Polar if you intend to charge other people to use your deployment.

Three environment variables: DATABASE_URL, BETTER_AUTH_SECRET, and BETTER_AUTH_URL. Everything else — email delivery, Google and GitHub sign-in, object storage, billing, scheduled jobs — is optional, and its absence hides the feature rather than breaking the app. A missing required variable fails at startup with a named error listing exactly what to set.

To whatever S3-compatible bucket you point S3_ENDPOINT at: Cloudflare R2, AWS S3, MinIO, Backblaze B2, DigitalOcean Spaces, or Tigris. The bucket stays private; files are uploaded straight from the browser to a presigned URL and downloaded through short-lived signed links. Leave the variables unset and the attachments interface is simply absent.

No — v2 is a fresh install, not a drop-in replacement. The identity provider changed, and a Kinde identity cannot become a Better Auth user without a credential reset, so there is no automatic data migration. v1 remains supported on its own branch and tag. docs/UPGRADING.md sets out what a migration would involve.

No. The licence grants you unlimited deployments for your own organization, commercial use, and the right to modify and rebrand — but not to redistribute the source, resell it, or publish it as a template. If you build for clients, each client organization needs its own licence. Other terms are available on request.

The action is refused with a message naming the plan, the limit, and your current count — for example, 'The Free plan allows 10 projects, and this organization has 10.' Archived projects do not count toward the limit, so archiving clears it without destroying work.