Introduction

ApisKit is a complete SaaS platform, written in Next.js 16 and TypeScript, that you buy once and download in full. It is not a skeleton and not a demo: it is the infrastructure every SaaS repeats, already built, already wired and already tested, so that you start with your product instead of with a sign-up form.

What you are looking at is the product

The page you arrived through, and this documentation section, are not a storefront built separately to sell you something. They are the template itself, running. The same code you download is the code serving this website.

That means you can check before paying what elsewhere you are asked to take on faith: sign up, open your profile, file a support ticket, switch language, see how it behaves on a phone. What you try here is what lands on your machine.

There is exactly one difference, and it is deliberate: the demo does not send real emails. The flow looks the same on screen, but no message goes out, so it costs nothing and fills no inbox. In the template you download that limit does not exist and email is sent normally.

What you receive

The full source of the repository, under a commercial licence, as a download. No subscription and no dependency on a server of ours: once you have the files, the product is yours to build and deploy.

Inside, working and wired together:

• User accounts. Sign-up, sign-in, email verification and password recovery, with Firebase Auth.
• Billing and credits. Stripe Checkout, a signature-verified webhook, credit packs and a wallet with its ledger.
• Admin panel. Role-protected: users, support, payments, contacts, newsletter, webhooks and the public documentation.
• Support system. Tickets with automatic diagnosis, escalation to a human, a conversation thread with attachments, and an admin inbox.
• Public documentation. The section you are reading, written from the panel in both languages.
• English and Spanish everywhere: interface, emails, errors, administration and legal texts, with a checker that stops one language falling behind.
• Search visibility. Metadata, Open Graph, sitemap.xml, robots.txt, JSON-LD structured data and llms.txt for language models.
• Legal texts for privacy, cookies, terms, payment conditions and legal notice, as samples to adapt.
• Eighteen automated checks under a single command.

What you will not have to build

The tally of what repeats in every project and never gets billed to a client: sign-up with email verification, the "I forgot my password" flow, the payment integration with its idempotent webhook, the panel to see what is happening, the ticket system with its email templates, full translation into two languages, the metadata on every page, and the database security rules.

None of that differentiates your product, and all of it has to be done anyway.

What you do have to bring

Honestly, because this is what decides whether ApisKit is useful to you:

• Your product. ApisKit brings the infrastructure, not your idea. The part that makes money is the part you write.
• The provider accounts. Firebase, Stripe and an email provider. The template includes neither their keys nor their billing.
• Real legal texts. The ones included are samples, not legal advice. Before you sell, a professional has to review them.
• Your brand. Name, colours, images and copy. One command does most of the work, but the decisions are yours.

Where to go next

If you are setting it up now, go to Installation and deployment. If you want to understand how it is built first, go to Architecture. If what you want to know is how much work it takes to make it yours, go to Make it yours.

And if what you are after is the price and what each option includes, it is on the pricing page.