Legal

License

Last updated August 23, 2026. This covers the One Shot source code itself. Your use of the website and your account is covered by the Terms. Licensor: Binns Pte. Ltd.

1. What you build is yours

We claim no rights whatsoever in anything you create with One Shot. Your code, your product, your customers, your revenue, your company. You owe us nothing beyond the license fee, you never owe us a share, and you don't have to credit One Shot (though we always like to hear about it).

This is true whether you're a person building a side project or a company shipping something commercial. Explicitly fine, no extra permission needed:

• Building products your company sells, at any scale or price.
• Building on it inside a startup, an agency, or a large business.
• Building client work you hand over, and charging whatever you charge.
• Keeping your source private, or open-sourcing your own application (see §4 for the one caveat).
• Being acquired, raising money, or selling the business you built on it.

2. What you're buying

Access to the One Shot source code, and a worldwide, non-exclusive, non-transferable right to use it as the starting point for software you build. You're buying a license to use it, not ownership of One Shot — copyright in the kit itself stays with Binns Pte. Ltd. That distinction only ever matters for §4.

3. What you may do with the kit

• Use it to build an unlimited number of applications, personal or commercial.
• Change any part of it, however much you want. You never have to publish those changes.
• Deploy those applications publicly and charge your own customers for them.
• Have your employees and contractors work on your copy, as part of building your applications.
• Keep using every copy you've already downloaded, permanently, even after your access ends.

4. The one thing you may not do

Don't pass One Shot itself on to people who haven't bought it. That's the only real restriction here, and it exists for an obvious reason: one person buying a copy and handing it to everyone else is the one thing that makes it impossible to keep building this.

Concretely, that means don't:

• Redistribute, resell, sublicense, or give away the kit's source, in whole or in meaningful part, whether or not you charge.
• Publish it where others can obtain it — a public repository, a file host, a course, a paid community.
• Share your repository access or account credentials outside your own company.
• Repackage it as a starter kit, template, boilerplate, or scaffold, free or paid.
• Claim you wrote it, or strip the copyright notices from the source.

The test: if someone would want what you're distributing because it is One Shot, rather than because of the product you built on top of it, that's the line. Open-sourcing your own app is fine — just not when what you're really publishing is the kit with a thin layer over it.

5. Teams and companies

Use it in as many of your company's products as you like — there's no per-product or per-deployment fee, ever, and no cap on users, servers, or revenue.

Licenses are counted by developers who need the source, not by products. Each license grants repository access to one GitHub account at a time, so if several people on your team want to pull updates themselves, buy a license for each. Nobody needs a license to use, run, or pay for the app you build.

6. Access and updates

While your license is active you can pull new releases as they ship. If it lapses, is refunded, or is charged back, repository access is removed and you stop receiving updates — but anything you already downloaded remains yours to use under this license, forever. The subscription buys continued access and updates, not the right to keep using what you have.

7. Open-source components

This license covers the original code that makes up One Shot. It does not cover, and cannot grant you anything in, the open-source software the kit is built on — Ruby on Rails, Hotwire, the gems in the Gemfile, the JavaScript in the importmap, and everything those depend on in turn. Each of those remains the property of its own authors and is governed by its own license, which travels with it and which you agree to by using it. Nothing here adds to, removes from, or overrides any of them.

Those licenses are permissive open-source terms (MIT and similar), which is why the kit can exist — but they are not ours to modify, and reviewing what you ship is your call to make. Names and marks like "Ruby on Rails" belong to their respective owners; One Shot is an independent product and isn't affiliated with, endorsed by, or sponsored by any of them.

8. Refunds

You can have your money back for any reason within 30 days of your first payment. Write to [email protected] and we'll refund it in full. A refund or a chargeback ends your repository access, as described in section 6. The copies you have already downloaded remain yours under this license.

The guarantee covers your first payment, not renewals. Cancel from your billing portal before a renewal charge if you don't want another year.

9. No warranty

The code is provided "as is", without warranty of any kind, express or implied, including merchantability, fitness for a particular purpose, and non-infringement. You are responsible for reviewing, testing, and securing anything you deploy, and for the keys and third-party services you connect to it.

10. Liability

To the fullest extent the law allows, Binns Pte. Ltd. is not liable for lost profits, lost data, business interruption, or any indirect or consequential damages. Our total liability is capped at what you paid for your license in the twelve months before the claim.

11. Ending the license

Breach section 4 and this license ends immediately, without refund, and you must destroy every copy you hold. Sections 1, 9, and 10 survive — you keep owning what you built.

12. Changes

We may revise this license for future purchases. The version in force when you bought is the one that governs your purchase — so a later change can't retroactively narrow what you're allowed to do with a copy you already have.

13. Questions

If you're unsure whether something is allowed, just ask — [email protected]. We'd rather answer than have you guess.