A decade in production — documented, not dramatized.
Our story is a timeline of facts you can check, not a founding myth. The engine behind Everythink has been live since 2016. What follows is exactly what shipped, what was a pilot, and what is still on the roadmap — each year carries its real honesty state, and we never round one up.
The team that kept one engine in production.
No founding myth — just the people at Everythink who shipped, fixed and documented each year on the timeline below. Headshots are placeholders for now; the names and the work are real.
Engine & vision
Carried Everythink from the 2016 origin to the Everythink Studio repositioning.
Platform engineering
The geospatial topology and the conversational engine, module by module.
Research & rigor
The 2026 backend audit and the 21-paper academic series with DOI references.
Pilots & partners
The 2022–2024 relationships we learned from — pilots, not a claim.
Illustrative — real team photos coming soon.
From Everythink to Everythink Studio.
One engine, ten years, told as a timeline. Production years are marked Production, the pilot era is marked Partial, and the future is marked Roadmap — honestly, in that order.
The origin Production
Everythink is born — the engine that powers Everythink today. From day one it ships a geospatial topology (network → community → room, each level a real polygon), a conversational engine of typed questions, and real-time chat. It goes straight into production. The space was the router from the very first release.
The build-out Production
The engine grows module by module: matchmaking between communities, marketplace, social (posts and stories), a calendar with a services agenda, and multichannel campaigns. Every module is switched on by configuration — no code. Five years of composable capabilities, all of them production. In 2019 the UK Government's Global Entrepreneur Programme (Department for International Trade) evaluated the technology and offered its support for the company's global growth strategy from a UK headquarters. Documented in the programme's letter of 28 July 2019, signed by Mark-Anthony Fevrier, Programme Manager, Global Entrepreneur Programme ([email protected]).
First external validation Production
Everythink is presented at the AWS AI Challenge, documenting the use case for conversational assistants serving networks of businesses — the topology and engine put in front of an outside technical audience for the first time.
Pilots and learning Partial
Early relationships and pilots — Somos Pileros, PDIE, 18-07 and Active Human Talent — test the whitelabel model and the recruitment/certification flow on top of rooms. These were pilots and partnerships, not a finished commercial motion, so this era stays Partial ⚠️: real deployments we learned from, not a production claim.
Everythink Studio
The engine is repositioned as Everythink: a no-code AI operating system. Pitch deck v2 (December 2025) sets the thesis — whitelabel networks plus a super app that connects them. The name changes; the engine underneath is the same one that has been running since 2016.
The year of rigor Production
The year we turned our own engineering inward and wrote the proof down. Three things landed:
- ✓Full backend audit by reverse engineering — module-by-module SDD, 17 bugs fixed, and technical debt catalogued and prioritized in public. Transparency, not marketing. ✅
- ✓A 21-paper academic series — P0 + the A core + the C sectors + the E1 evaluation + P-C10 community credit. Theorems backed by DOI-verified references, with the discipline of honesty itself formalized as a theorem. ✅
- ✓Enterprise proposals and a published roadmap — multi-local conversational commerce is in proposal, while federation, the wallet/token and community credit are Roadmap, design 2026+. 🔵
What is next Roadmap
Reactivating the matchmaking scoring, integrating payment rails, and shipping P-E1 telemetry so we can turn every "designed" claim into a "guaranteed" one — and only then, the financial layer on top. This is the published roadmap, not shipped work: it stays Roadmap 🔵 until the mechanism is built and measuring.
Ten years, stated as facts.
No invented KPIs — just the structural facts behind the timeline above.
Honesty is the through-line, not the footnote.
A history page is the easiest place to inflate a story. We do the opposite: each year carries the same Production / Partial / Roadmap label we use in our papers and our pitches.
A property is guaranteed exactly when its mechanism is implemented and measuring.
That is the literal statement of the honesty theorem in our overview paper, and it is why 2016–2021 read as Production, the 2022–2024 pilots read as Partial ⚠️, and federation, the wallet/token and community credit read as Roadmap 🔵. We would rather a year look conservative than claim something that was only a pilot.
What is on the roadmap is not built yet
The financial layer — federation between networks, the per-network token wallet and community credit — is design 2026+, pre-revenue, and not implemented. We will not present it as Production at any point on this timeline, and any token or credit mechanism remains subject to the applicable financial and securities frameworks (including the Howey analysis) before it ever launches.
Roadmap concepts, not shipped screens — join the waitlist on the changelog →
The people, the proof and the present.
The timeline is the backbone — here is where the rest of the story lives.
Who we are
The team at Everythink that has kept this engine in production since 2016, and the beliefs that shaped each year above.
Who we are →
About us · the Golden Circle
Why we exist, how we work, and exactly what we offer — with the same honesty system applied to every claim.
About us →
The 2026 changelog
What shipped, what was fixed, what was removed, and the known issues — the rigor year, line by line.
Changelog & roadmap →A decade of production — and a roadmap stated honestly.
See the engine that has been live since 2016, walk the network → community → room topology, and check the real state of everything on the roadmap.