Skip to content

MakerKit

MakerKit sells editable starter projects for subscription web apps. Its Next.js and Supabase kit includes sign-in, team accounts and billing integration code.

Visit MakerKit

What does the Supabase kit give you on day one?

The kit supplies screens and code for personal and team accounts, invites and subscription billing. The Next.js Supabase version uses Supabase for sign-in, records and file storage. The vendor also sells kits with a different database and sign-in setup.

The local setup guide uses Docker to run the sample services on your computer. To go live, your team has to connect its own Supabase project, selected billing provider and host. Check what will send email before trying an invite.

Can you take the files with you or hand them to a client?

MakerKit charges once for the selected kit and provides access to its private source repository. Pro covers one developer, and Teams advertises up to five collaborators. Hosting and connected services have their own costs.

Keep your product repository private. MakerKit’s license restricts sharing the kit or derivatives, and describes separate requirements for client source handoffs and dedicated client deployments. Check the actual license for your setup before paying.

How do starter updates reach your edited app?

Keep your own copy of the code under version control. MakerKit documents connecting that copy to the original kit so you can bring in later changes. Review changes in a separate copy first. A change to team roles or billing can affect behavior you customized.

Keep a record of the kit version, your database changes and who controls each connected account. Test an invite, a permission boundary and a billing-state change against disposable services before release.

How would you decide if the included team roles fit?

Draw a fictional workshop scheduling app. Do not open an account or send an invite.

  1. Draw two roles
    Give the owner access to billing and let a helper see only the workshop schedule.
  2. Write the denied action
    Mark a billing change the helper should be unable to make. Put the expected result next to it.
  3. Mark the handoff
    List who would own the project, database and billing accounts. The paper exercise leaves permissions and billing untested.