Skip to content
Keel
Legal

License Agreement

Version 2.0 · Effective October 21, 2026

This License Agreement (the "Agreement") is between Mohsin Akram, operating as Keel ("we", "us"), and the person or company that bought a Keel license ("you"). It covers the Keel source code, components, configuration, documentation and any updates we give you access to (together, "Keel").

By buying, downloading, cloning or using Keel you agree to this Agreement. You can read it before you buy at https://keelkit.dev/license. If you don't agree, don't buy or use Keel.

The short version

This summary is here to make the terms easy to read. If it ever disagrees with the numbered sections below, the numbered sections win.

Every tier

  • You can build and sell as many of your own products with Keel as you like.
  • You can change the code however you want.
  • You don't have to credit Keel anywhere in what you ship.
  • You can never sell, share or publish Keel itself, or a starter kit built from it.

Solo, $199

  • One developer.
  • Your own products only. No paid work for clients.
  • A zip of the code as it stood on the day you bought it. No future updates are included.

Studio, $349

  • Everything in Solo.
  • Your whole team can use it.
  • Paid client work: you can build a product for a client and hand it over.
  • Read access to the private GitHub repo, with ongoing updates for as long as we maintain Keel.
  • Private email support.

Agency, $899

  • Everything in Studio.
  • Multi-project and white-label rights: you can deliver the same Keel-based product to many clients, or sell it under your own brand.
  • Priority support.

1. Definitions

1.1 Product means a working application, website or service built with Keel, where Keel is part of a larger application you've built and not the thing being sold.

1.2 Project means one Product with its own codebase, aimed at one purpose. Staging, preview and production deployments of the same codebase, and different regions or domains running it, are still one Project. A copy of the codebase changed or rebranded for a different client or market is a separate Project.

1.3 Your Own Product means a Product you own and run, or sell to end users, for your own business.

1.4 Client Project means a Product you build for someone else (a client or an employer) as paid or contract work, where the finished Product is handed over to them.

1.5 White-label means delivering a Product under your brand or your client's brand, or delivering the same or a substantially similar Product to more than one client.

1.6 Developer means a person who reads, changes or works with Keel's source code.

1.7 Your Organization means you, or the company you bought Keel for, along with its employees and contractors working on its Products.

2. License grant

Once you've paid, and as long as you follow this Agreement, we give you a worldwide, non-exclusive, non-transferable, perpetual license to use Keel as described for your tier below. Perpetual means your right to use the version of Keel you have doesn't expire, even if your access to updates ends.

2.1 Solo

  • One Developer may use Keel.
  • You may build any number of Your Own Products and run, sell or monetize them commercially.
  • You may not use Keel for Client Projects or any other paid work for someone else.
  • You get a zip of Keel as it stood at the time of purchase. Future updates are not included. If you want them, you can upgrade to Studio by paying the difference.

2.2 Studio

  • Everything in Solo.
  • Any number of Developers in Your Organization may use Keel.
  • You may build any number of Client Projects and hand each finished Product over to its client, including the source code of that Product.
  • You may not White-label: each Client Project is built for one client, and the same Keel-based Product can't be delivered to several clients or sold as a branded, repeatable offering.
  • You get read access to the private Keel GitHub repository for the GitHub account named at checkout, with ongoing updates (see Section 6).

2.3 Agency

  • Everything in Studio.
  • You may White-label: deliver any number of Projects to any number of clients under your own or your clients' branding, including the same or a similar Keel-based Product for several clients.
  • You may resell or license finished Products built with Keel to your clients as your own work.
  • Agency covers the Products you build. It does not cover Keel itself. Section 4 still applies in full.

3. What every tier may do

3.1 Change the code. You may modify, extend and refactor Keel without limit, for use inside your Products.

3.2 Sell what you build. You may sell, license or run your Products commercially, within the limits of your tier.

3.3 No attribution. You don't have to mention Keel or us in your Products, their interface, their code or their documentation. You may remove Keel branding from anything you ship.

3.4 Hand-over to clients. Where your tier allows Client Projects, the client may receive, keep and keep changing the source code of the Product you built for them. They may not reuse the Keel parts of that code to start other Products unless they buy their own license.

4. What no tier may do

Whatever your tier, you may not:

4.1 Sell, resell, sublicense, rent, lend, give away or otherwise distribute Keel, or any substantial part of it, as source code, a template, a boilerplate, a starter kit, a scaffold, a code generator or a component library, whether paid or free.

4.2 Publish Keel's source code where people outside Your Organization (or, for a Client Project, outside the client) can read it. This includes public GitHub or GitLab repositories, package registries, gists, file shares and forums. Keep any repository that contains Keel private.

4.3 Build or sell a product that competes with Keel, meaning anything whose main value is Keel's code, structure or setup rather than a working application built on it.

4.4 Share Keel with anyone who hasn't bought their own license, except Developers in Your Organization (Studio and Agency only) and clients receiving a finished Client Project under Section 3.4.

4.5 Share your access to the private repository, add other accounts to it, or mirror it to another location others can reach. If you need to change the GitHub account, email us.

4.6 Remove or change this Agreement or the ownership notices in Keel in a way that hides where Keel came from or how it's licensed.

Sharing a finished, deployed app you built with Keel is always fine. Sharing Keel, or a thin wrapper around it, is not.

5. Ownership

Keel is licensed to you, not sold. We keep all rights in Keel, including its original code, design system and documentation. You own the code you write and the Products you build, but not the Keel code inside them.

6. Updates and support

6.1 Solo is a snapshot. You get the version available on the day you bought it, and no updates.

6.2 Studio and Agency get ongoing updates through read access to the private repository for as long as we maintain Keel. You pull updates when you choose. We note changes in the changelog and try not to ship breaking changes without saying so.

6.3 Ongoing updates are not a promise to build particular features or to maintain Keel for any fixed period. If we stop maintaining Keel, we'll say so on the changelog, you keep your license to the latest version you have, and we'll keep your repository access open for at least 90 days after that notice so you can take a final copy.

6.4 Repository access belongs to the GitHub account given at checkout. We may remove access if this Agreement is breached or the purchase is refunded or reversed.

6.5 Support levels are those listed on the pricing page for your tier when you bought it. Support is help with Keel as documented, not custom development.

7. Refunds

7.1 You can ask for a refund within 14 days of purchase by emailing support@keelkit.dev with your order number.

7.2 We'll refund you in full if Keel doesn't work as its documentation describes, or if you can't get a documented flow running (local setup, sign-in, billing, deploy) after contacting support and giving us a fair chance to help you fix it.

7.3 If you haven't downloaded the zip or accepted the repository invite yet, you can cancel for any reason within those 14 days.

7.4 Once you've downloaded the zip or accessed the repository, a change of mind isn't grounds for a refund, because source code can't be given back.

7.5 When a refund is issued, or a payment is reversed or charged back, your license ends, repository access is removed, and you must delete your copies of Keel.

8. Third-party software

Keel uses open-source packages and outside services (for example Next.js, Better Auth, Drizzle, Stripe, LemonSqueezy, Polar, Resend and Upstash). Each one is covered by its own license and terms, not by this Agreement. You're responsible for following those terms, and for any accounts or fees with those services.

9. Termination

9.1 This Agreement starts when you first download or use Keel and lasts until it's ended.

9.2 We may end it if you materially breach it and don't fix the breach within 14 days of our notice. A breach of Section 4.1, 4.2 or 4.3 can't be fixed, so for those we may end it straight away.

9.3 When it ends, you must stop using Keel and delete your copies, and any repository access is removed. Products you lawfully built and shipped before then may keep running, but you may not keep building on Keel. Sections 4, 5, 8, 10, 11 and 12 continue after it ends.

10. No warranty

KEEL IS PROVIDED "AS IS", WITHOUT ANY WARRANTY, EXPRESS OR IMPLIED, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. WE DON'T WARRANT THAT KEEL IS ERROR-FREE OR SECURE, OR THAT IT MEETS YOUR NEEDS. YOU'RE RESPONSIBLE FOR TESTING AND REVIEWING EVERYTHING YOU SHIP, INCLUDING ITS SECURITY AND LEGAL COMPLIANCE. THIS DOESN'T LIMIT YOUR REFUND RIGHTS UNDER SECTION 7.

11. Limitation of liability

TO THE EXTENT THE LAW ALLOWS, WE ARE NOT LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, REVENUE, DATA OR GOODWILL, ARISING FROM THIS AGREEMENT OR KEEL, EVEN IF WE WERE TOLD THEY WERE POSSIBLE. OUR TOTAL LIABILITY UNDER THIS AGREEMENT IS LIMITED TO THE AMOUNT YOU PAID FOR YOUR LICENSE.

Some places don't allow some of these limits, so parts of this section may not apply to you.

12. General

12.1 Governing law. This Agreement is governed by the laws of the State of Delaware, USA, without regard to its conflict-of-laws rules.

12.2 Whole agreement. This Agreement and the Terms of Service at https://keelkit.dev/legal/terms are the whole agreement about Keel. If they conflict about what you may do with the code, this Agreement wins.

12.3 Changes. We may publish new versions of this Agreement for future purchases. The version in force when you bought keeps applying to your purchase unless you agree to a newer one.

12.4 Severability. If any part of this Agreement can't be enforced, the rest still applies.

12.5 No waiver. Not enforcing a term once doesn't mean we've given it up.

12.6 Transfer. You may not transfer this license without our written consent. We may transfer this Agreement as part of a sale or merger of the business.

12.7 Contact. Questions about licensing: support@keelkit.dev.