Fake Company Generator
Generate believable company names, domains and details for mockups.
Pick an open source licence and get a LICENSE file with your details.
The License Generator sets sixteen open source licences side by side — what each permits, requires and limits — and produces a ready LICENSE file with your name and year, or the official source-file notice where the full text must be copied verbatim.
Sixteen licences, each with the permissions it grants, the conditions it attaches and the limitations it keeps — set side by side so the choice is made on what the licence actually does rather than on which name is most familiar.
The short permissive licences and Apache 2.0 are reproduced here in full, with your name and year filled in, ready to save as LICENSE. The GNU family, MPL and CC0 are different: they run to tens of thousands of characters and are meant to be copied verbatim from their canonical source, because a licence that has drifted by a word is arguably not that licence any more. For those, this generates the official source-file notice — the part that carries your details — and tells you exactly where the full text comes from.
Permissions, conditions and limitations for each licence, so the choice is made on substance rather than on which name is familiar.
The GPL family, MPL and CC0 must be copied verbatim from their canonical source. The page says so and gives the URL, rather than shipping a text typed from memory.
Several licences expect a short header in every file as well as the LICENSE — that notice is generated with your details filled in.
Including the appendix, with your name and year substituted into the boilerplate at the bottom.
The exact string to put in package.json, Cargo.toml or composer.json, which is what tooling reads.
Each one lists what it permits, what it requires of anyone using your code, and what it does not cover.
Your name or your company, the year, and the project name where the licence needs it.
Save it as LICENSE, with no extension, in the root of your repository.
Some licences also expect a short notice at the top of each source file — that is generated too.
Copyright still applies, so by default nobody may copy, modify or distribute it. "Public on GitHub" is not a licence — without one you have technically given visitors permission to view the code and nothing else.
Apache 2.0 is MIT plus an explicit patent grant and a clause that terminates it if the user sues you over patents. If patents could plausibly be involved, or a corporate legal team will review your project, choose Apache. Otherwise MIT is shorter and understood by everyone.
Because it is 35,000 characters that must match the canonical version exactly, and shipping a copy typed out from memory would be worse than useless. The page gives you the notice for your source files and the exact URL the LICENSE file should come from.
For future versions, yes, if you own all the copyright. Contributions from other people are licensed under the terms in place when they were made, so relicensing a project with outside contributors means getting each of them to agree.
What people who use the License Generator think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the License Generator. It takes half a minute and no account.
Write the first reviewGenerate believable company names, domains and details for mockups.
Build and edit URL query strings without breaking the encoding.
Check a JWT signature against a secret or a public key, and see why it fails.
Estimate how long a password would survive, and see exactly what weakens it.
Inspect any character: code point, block, category, UTF-8 bytes and escapes.
Re-indent HTML without breaking whitespace-sensitive elements.
Generate the border trick that makes triangles and tooltip arrows.
Convert between bytes, KiB, MB, GB and bits, in both systems.