nocode: A Satirical Zero-SLOC Application Stack That Actually Deploys Nowhere
GitHub describes it as The best way to write secure and reliable applications. Write nothing; deploy nowhere.. The repository metadata lists Dockerfile as its primary language. The metadata lists the Apache-2.0 license. This article stays within the project description and details documented in the GitHub repository README.
At a glance
- What is it?
- Kelsey Hightower's nocode repository is a joke repository that demonstrates how to build, deploy, and scale an application by doing nothing. It offers no code, no deployment, and no security surface, but it also has no functionality.
- Who is it for?
- Adopt nocode if you want a joke for your next conference talk or a way to illustrate the absurdity of over-engineering. Do not adopt it for any real workload, because it has no executable output, no deployment target, and no feature set.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Probably not. The repository last received commits 27 months ago, on August 7, 2024.
- What is it written in?
- Mainly Dockerfile, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- kelseyhightower/nocode66,058 ★ · +449
| Repository | 2026-08-13 | 2026-11-15 |
|---|---|---|
| kelseyhightower/nocode | 65.6k | 66.1k |
449 Stars in the last 94 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What nocode Actually Solves
nocode solves a problem that does not exist, and that is the point. The README presents it as 'the best way to write secure and reliable applications' because it contains no code to be insecure or unreliable. The repository is a parody of software development tutorials, with empty code blocks and commands that produce no output. It is for developers who appreciate humor in a field that often takes itself too seriously. The target audience is not a production engineer but a presenter, a teacher, or anyone who wants to make a point about the complexity of modern stacks. The problem it addresses is the tendency to add layers of tooling where none are needed.
The Mechanism: Absence as Architecture
The repository's architecture is defined by what it lacks. There is no source code, no build script, and no deployment manifest in the README. The 'Getting Started' section shows an empty code block, and the 'Building the Application' section shows another empty block, followed by the claim that you will see output, which is also empty. The deployment step tells you to run a command that deploys 'absolutely nowhere.' Scaling is equally absent. The mechanism is pure negation: every action produces nothing, and the only data flow is the reader's imagination. The README even includes a blank code block labeled as an example application, suggesting it could do anything you want, but it does nothing. This is a deliberate design choice that mirrors the structure of a tutorial while subverting it.
Getting It Running: Commands That Do Nothing
The README provides no actual commands, only empty code fences. The instructions are: 'Start by not writing any code,' then 'build your application' with a command that is not shown, and 'deploy your application' with another unshown command. The only concrete command in the README is 'You don't' for contributing. To run this project, you clone the repository and look at the README. The Dockerfile contains only `FROM scratch`, and there are no executable files. The only release is 1.0.0, from February 2018. In practice, running the project means doing nothing, which is the intended behavior. If you want to verify, you can run `git clone https://github.com/kelseyhightower/nocode` and then `ls` to see its five files, but the README does not suggest this.
Where nocode Is the Wrong Tool
The obvious limitation is that nocode produces no software. If you need a web server, a CLI tool, or a library, this repository will not help you. It also has no maintenance path: the last push was on 2024-08-07, and the repository is not archived, but it is effectively frozen. The 'Contributing' section says 'You don't,' which closes the door to community involvement. As a satirical piece, it fails if taken literally. A developer who clones it expecting a working application will be disappointed, and a manager who sees 'deploy nowhere' in a proposal will rightly reject it. The repository is the wrong tool for anything that requires actual computation, storage, or user interaction. It is also the wrong tool for teaching beginners, because it reinforces the idea that code is unnecessary, which is a harmful misconception outside the joke.
A Real Alternative: The Empty Repository vs. A Minimal Hello World
A real alternative is the classic 'hello world' in any programming language, such as a single Python file that prints 'Hello, World.' The difference is that a minimal program has a tangible output and can be run, tested, and extended. nocode has no output at all. Another alternative is an empty Git repository with a README that states the project's purpose, which is what nocode essentially is, but without the satirical framing. The key difference is that alternatives provide a starting point for real work, while nocode provides a punchline. If you want a joke, nocode works. If you want a minimal viable product, even a one-line script is more useful. The contrast is sharp: one has zero lines of code and zero features, the other has one line and one feature.
Maintenance, Licensing, and the Cost of a Joke
The repository is licensed under Apache-2.0, which means you can use it freely, but there is nothing to use. Maintenance is non-existent: the last push was on 2024-08-07, and the 'Contributing' section explicitly says 'You don't.' This means there is no upgrade path and no support commitment. The cost of adopting nocode is the time you spend explaining that it is a joke. If you include it in a dependency tree, it would add nothing but confusion. The license is permissive, so you can fork it and add your own code, but that would defeat the purpose. The release 1.0.0 is the only release. For a real project, this would be a red flag; for a satire, it is part of the humor. The maintenance cost is zero because there is nothing to maintain, but that is also the reason it cannot meet any real requirement.
Editorial conclusion
Adopt nocode if you want a joke for your next conference talk or a way to illustrate the absurdity of over-engineering. Do not adopt it for any real workload, because it has no executable output, no deployment target, and no feature set. Before using it, verify that your audience understands satire, and be aware that its last push was on 2024-08-07 and its only release dates from 2018. If you need a real application, choose an actual framework; if you need a lesson, nocode is the right tool.
Frequently asked questions
What is NoCode?
In general a no-code platform is a way to build applications without writing code. This repository is a joke rather than a platform: it is the kelseyhightower/nocode project, whose description reads The best way to write secure and reliable applications. Write nothing; deploy nowhere.
What does the Dockerfile in this repository actually build?
Its only line is FROM scratch, which is Docker's empty base image with no filesystem, shell or libc. An image built from it contains just what you copy in, and this one copies in nothing, so the result is an empty image rather than a runnable application.
Are there any commands I can copy from this README to get started?
No. All six code blocks in the README are empty. The surrounding text tells you to start by not writing any code, to build by not doing anything, and to deploy absolutely nowhere, so the blank fences are the joke rather than an omission.
Is this repository suitable as a starting point for a real application?
No. The repository contains five files, CONTRIBUTING.md, Dockerfile, LICENSE, README.md and STYLE.md, with no source, tests, build or dependencies, and the last push was 2024-08-07 with one release tagged 2018-02-07. It is a written joke, not a template.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/kelseyhightower-nocode)Star history chart for your README
[](https://hysenlabs.com/projects/kelseyhightower-nocode)Was this useful?