λ

Abstract Algorithm

the manifesto

An abstract algorithm is a pattern you can see before you can name it — a thing that should exist in the world and doesn't, or exists only behind a paywall so high that the people who need it most will never get through.

We find those patterns and we build them. Not as products first. As tools — the kind you own, run on your own metal, open up, and repair. Everything on this site came out of that habit.

Present primitive. Get underestimated. Outthink them.

— the whole strategy, in six words

What we are actually mad about

Software stopped being something you owned and became something you rented, and almost nobody objected. The blacksmith owned the anvil. You lease your CRM by the seat, and the day you stop paying, your customer list is hostage.

The second thing: complexity became a proxy for seriousness. A stack nobody can hold in their head is treated as more professional than one a single person can maintain. It isn't more professional. It is just harder to leave — which, for the vendor, is the point.

The third thing, and the one that actually costs people their businesses: enterprise pricing is set by what a procurement department will tolerate, not by what the software costs to run. A restaurant paying $400 a month for a point-of-sale system is subsidizing a sales org, not a kitchen.

The doctrine

I

Own the tool or you don't own the business

Self-hosted, source-visible, exportable. If we vanished tomorrow, everything we shipped would keep running on hardware you control.

II

If it needs 47 YAML files to deploy, it's wrong

Complexity is a cost, and the person paying it is usually not the person who chose it. Vanilla until vanilla genuinely stops working.

III

The free tier is free, not bait

No card, no trial clock, no feature that quietly stops working on day fifteen. If it says free, it stays free.

IV

Mom and pop keep 92%+

A platform that takes a third of a small shop's revenue isn't infrastructure, it's a landlord. Our cut is small on purpose.

V

Build the boring half

Auth, backups, invoices, tax lines, receipt printers. The unglamorous parts are where real businesses actually break.

VI

Say the true number

Real counts, real prices, real limitations, including the ones that make us look smaller. A demo that lies is a debt you pay later.

Where the work lives

The same engine, the same identity, different doors depending on who is walking in.

The Temple
knuckledragger.tech
Hardware, engines, APIs. Show me what you built.
The Mall
ewepip.com
The marketplace. Vendors, storefronts, shopping.
The Forge
ewepip.net
The workbench. Tools you use, not tools you browse.
The Front Porch
talentliberation.org
Free career tools. No account, no tracking, forever.
The Firm
upip.company
The enterprise skin. Same engine, suit and tie.
The University
upip.academy
Learn it, practice it in a simulator, get certified.

On being underestimated

The name is a joke that stopped being a joke. A knuckledragger is what people call you when you don't perform sophistication — when your stack is plain, your pages are hand-written, and your explanation of the architecture takes one sentence instead of a slide deck.

That reaction is useful. It buys time, it lowers guard, and it means nobody notices the thing being built until it is finished. Present primitive. The work is not primitive.

We are not trying to look like the future. We are trying to still be running in ten years, on hardware in a basement, owned by the people using it.

See What We Built Read the Philosophy The Stack