The desk has not changed in thirty years
The spreadsheet arrived in 1979 and never left. Everything since has been built around it rather than past it. epyx replaces it with a document that computes, shares and asks for what it is missing — authored by describing it, in plain language.
Why this was buildable now and not before
Two things had to be true at once, and only recently were.
A machine can assist in writing the code (but not the architecture)
The hard part was never running Python — it was that the person with the question could not write it. That barrier fell. epyx is what you build once it has.
A small team can build a large system
epyx was built by one person. That is not a note about our size; it is the product thesis, demonstrated by the company that holds it.
What exists today
A foundational patent, written by the founder
Filed April 2026, assigned to Epyx-AI LLC, covering the doclet architecture — the live dependency graph, composable controls, and the separation of logic from render.
A finished product, not a prototype
Doclets run real Python in a secure container. The four-and-a-half minute film on Say hello is a recording of the product, not a mock-up.
Your data never crosses our servers
Sharing is peer-to-peer by mandate. Our cloud does rendezvous only — it never carries document data. Local-first is architecture here, not a slogan.
A platform, not a single app
Editions let a vertical be branded and extended with native compute, built on the same core. One codebase, many industries.
Who is behind it, in full, is on the About page. The product itself is on Say hello.
This is our financial model
Scenarios, unit economics per tier, the annual roll-up, the funding rounds — every number driven live by the controls on the left.
It is not a spreadsheet and it is not a slide. It is an epyx doclet — and anyone could build it.