What you own
A transfer, not a tenancy.
Buying here ends the relationship rather than starting one. The repository becomes yours, the database is on your infrastructure, and nothing in the software reports back to us or expires if you stop paying, because there is nothing to stop paying.
Fixed price, in writing
Want one fitted to your process?
Tell us what you run today. You get a written scope and a fixed price back, not a discovery retainer.
The short version
One payment buys one application, transferred to your organisation in full. You may run it, read it, change it, extend it, rebrand it and deploy it as many times as your own business needs. You may not turn round and sell the source as a product of your own.
That is the whole of it. What follows sets the same thing out precisely, because a sentence a buyer can quote is worth more than a page they cannot.
Granted, and withheld
Two lists, and nothing hiding between them.
Yours on purchase
- The complete repository: application code, database schema, migrations and seed data
- The right to run it on any infrastructure you choose, for as long as you like
- Unlimited internal users, with no count to declare and no seat to buy
- The right to modify any part of it, including removing our name
- The right to deploy it for the entities your organisation controls
- The right to hire any developer to work on it, ourselves included or not
- The right to keep running it if we cease trading tomorrow
Not granted
- Reselling the source, or a close derivative, as a product or template
- Publishing the repository publicly, in whole or in substantial part
- Running it as a multi-tenant service for organisations you do not control
- Passing the code to a third party except a contractor working on your build
- Using our trading name to endorse software you have since changed
How far one purchase reaches
Most buyers never touch this. It matters if you are an agency or a group.
One organisation
The default. One purchase covers your company and any entity it owns or controls, across as many environments and offices as you run. Staging, production and a developer laptop are the same licence, not three.
Agency and client work
Deploying on behalf of clients needs the agency scope, priced per build rather than per client. It permits an installation per client on infrastructure they own. It does not permit one installation shared between them, which is a product, not a deployment.
The parts we did not write
Every application here stands on open-source software, and that keeps its own terms.
The framework, the database driver, the date library and everything else in the dependency tree arrive under their own licences, most of them MIT, BSD or Apache 2.0. Those licences are not ours to grant or to change, and our sale does not touch them.
Every delivery includes a generated manifest naming each dependency, its version and its licence, so the answer to "what is in this" is a file in the repository rather than an afternoon of reading. We do not ship anything under a copyleft licence that would reach your own code.
The terms themselves
Eight clauses. They govern; the plain wording above explains.
1 · Grant
On payment clearing, we assign to you a perpetual, worldwide, non-exclusive right to use, reproduce, modify and deploy the delivered source for your own business purposes, with the exclusions listed in clause 2.
2 · Exclusions
The right does not extend to distributing the source, or a work substantially derived from it, as a competing product, template or hosted service offered to organisations outside your control.
3 · Delivery
Delivery is the transfer of the repository to an account you nominate, together with the schema, migrations, seed data, deployment configuration and dependency manifest. Delivery completes the sale.
4 · Updates
Twelve months of updates from the delivery date are included. After that the code remains yours in full; only the flow of new work stops. Updates are offered, never pushed, and you decide whether to take one.
5 · Third-party components
Open-source dependencies are licensed to you by their own authors on their own terms. We warrant only that we have not knowingly included a component whose terms conflict with this agreement.
6 · Warranty
We warrant that the software matches its description at delivery and that we hold the rights we are transferring. Beyond that it is provided as it stands, without a warranty of fitness for a purpose we have not been told about.
7 · Liability
Our liability arising from the sale is limited to the amount you paid for the application. Nothing here limits liability for death, personal injury or fraud, which cannot be limited by agreement.
8 · Termination and law
The grant does not expire and we cannot revoke it for convenience. It ends only if you distribute the source in breach of clause 2. The agreement is governed by the law of the jurisdiction named on your invoice.
Questions
What owning it actually means
Not covered here?
Ask a consultant directly. No form to fill in first, and no follow-up sequence.
Book a consultantAll questionsIs there a licence key or an activation check?
No. There is no key, no phone-home, no seat count and no kill switch. Once the repository is yours the software has no opinion about whether you have paid, because nothing in it asks.
What happens to our software if you close down?
Nothing. That is the point of the arrangement. You hold the code and it runs on your infrastructure, so our continued existence is not a dependency of your operations.
Can we remove your branding?
Yes, and most buyers do. It is your codebase. The only thing you cannot do is keep our name on software you have changed, in a way that suggests we stand behind it.
Can we resell the application to our own customers?
Deploying it for a client on infrastructure they own is the agency scope. Selling the source itself, or a lightly changed version, as a product is the one thing clause 2 excludes.
Do we own changes our developers make?
Entirely, and we make no claim on them. Anything your team writes on top of the delivered code is yours alone.
Can we put the code in a private repository of our own?
That is where it belongs. Delivery is a transfer into an account you nominate, so it starts there.
Start here
Read the terms, then click through the software.
The licence describes what you get. The previews show what it is. Both are open, and neither asks for an email address.
- No sign-up to open one
- One-time price, no seats
- Source code transferred on delivery