Belief system
Eight beliefs that shape how nertia is built and priced.
The product is a direct expression of these beliefs. They are also how we talk about the work.
1. Incentive structures determine outcomes.
Every tool gets good, then gets greedy, then dies. That is not bad leadership — it is the structural logic of profit-maximizing entities. The only fix is changing the structure. That is what nertia is doing.
2. Community is the actual engine.
Not companies. Not founders. The community has always determined what becomes standard. Companies just monetize what the community already decided. nertia puts the community first structurally, not as a marketing move.
3. Small contributions compound into everything.
The internet you are using right now is billions of tiny decisions stacked on each other. You do not need to build the next Google. You need to add 2mm.
4. Shared abundance beats personal extraction.
If you help others ship, you win too. That is not altruism — it is the logical conclusion of believing in compounding contributions.
5. We are born into debt to the collective.
No matter how much you work to help others, it will never equal the help you received by just being alive today. Contribution is not optional — it is the only honest response to having been given a starting point at all.
6. The internet should be joyful.
Simpler, lighter, more fun. Somewhere along the way the web got corporate and heavy. That is a fixable problem.
7. AI is the frosting, not the cake.
Most AI website builders ask the model to reinvent React, design systems, and content from scratch on every prompt. That is how you get slop. nertia inverts it: standards and the community library carry the cake. AI carries the frosting — content polish, brand extraction from a URL, day-to-day maintenance. Reinventing the wheel every session is collaboration debt.
8. The composition JSON is the universal adapter.
nertia does not build features — it builds ports. Any capability that can read or write the portable site recipe plugs in. Input can be anything. Output is always the recipe. Result is always a site.
Keep reading
- Our story — the recipe model in plain language
- Architecture — how builder, CLI, and MCP share one engine
- Pricing — Build free, hosting and AI as flat fees