Open for work — taking new projects
Software engineering studio
We design, build, and ship production systems end to end — and the marketing and promotion that puts them in front of the right people.
New name. Deliberately small. Work speaks first.
AE·TH·RY·ON·EX·IS — the name is the thesis
01 / Services — nine disciplines
One studio, end to end. You don't hand off between a dev shop, a security consultant, and an agency — we cover the whole path from architecture to the campaign that launches it.
01 — AI Systems
LLM-backed tooling, retrieval pipelines, agents, and inference plumbing — built to be observable and debuggable, not demoed once and abandoned. Evaluation harnesses, prompt versioning, cost controls, and fallbacks for when the model is wrong.
02 — Automation
Replacing manual operations with systems. Pipelines, scrapers, orchestration, and automation layered onto software that was never built to expose an interface.
03 — Cybersecurity
Secure architecture, applied cryptography, threat modelling, and hardening. Designed to survive review, not to pass a checklist.
04 — Infrastructure
Deployment, hosting, and scale. Systems that stay up, degrade gracefully, and are cheap to operate — with the observability to prove it.
05 — Web
Interfaces and services, front to back, held to the same standard as everything behind them. Fast, accessible, and built to be maintained.
06 — Mobile
Native and cross-platform Android applications — offline-first where it matters, with real state management and release pipelines that don't break on launch day.
07 — Consultancy
Architecture review, technical due diligence, and a second opinion you can act on. We tell you what's actually wrong, what it costs to fix, and what you can safely ignore.
08 — Growth
Positioning, messaging, and go-to-market for technical products — plus the campaigns and channels that get the work seen. Measured, iterated, and honest about what moves the needle.
09 — Screening
Technical screening built by people who actually ship. Role-accurate assessments, structured rubrics, and signal on whether a candidate can do the work — not whether they memorised puzzles.
02 / Why us — what you actually get
Most teams get one of two things: a shop that builds fast and leaves you a mess, or a consultancy that writes a document and never ships. We do the whole thing, and we hand it back so you can run it without us.
Documented, reproducible, and yours to run. No proprietary lock-in, no dependency on us to keep the lights on. If you never call us again, everything still works.
Threat modelling and applied cryptography are part of how we build, not a phase we bolt on at the end. Signed payloads, race-safe writes, and real auth on day one.
You talk to the engineer building your system — not an account manager relaying messages. Fewer people, less translation loss, faster decisions.
Nothing sits unmerged for a month. You see working software early and often, which means you can change your mind before it gets expensive.
Tests, failure modes, and observability are part of the deliverable. When your investor's technical advisor opens the repo, it holds up.
If your idea has a fatal flaw, we say so before you pay us to build it. If something is cheaper to buy than build, we tell you that too.
What clients say — anonymised at client request
They found a race condition in our order assignment that we'd been blaming on drivers for months. Fixed it in two days and then showed us how to test for it ourselves.
We came in wanting an app. They pushed back and scoped the actual problem first, which cut the build in half. The handover docs were good enough that our own developer picked it up cold.
Delivery addresses used to be spoofable and we didn't know. They signed them, explained exactly why it mattered, and it hasn't been an issue since.
03 / Work — selected builds
Bakery delivery · production
A bakery delivery application built around three roles — customer, owner, and driver. Real-time ordering, live driver tracking on routed maps, tamper-proof delivery addresses, and race-safe order assignment, built to stay correct under real traffic.
React · Node.js · Socket.IO · MongoDB · OSRM
We keep client work private — more can be walked through on a call.
04 / Process — scope to hand off
Five phases, every engagement. You always know which one you're in, what comes out of it, and what it costs you to change your mind.
Understand the system before touching it. We map what exists, what actually hurts, and what success looks like in measurable terms.
Deliverable Written scope, constraints, and a fixed estimate.
Decide the tradeoffs explicitly and write them down — what we optimise for, what we deliberately give up, and the failure modes we accept.
Deliverable Architecture doc, data model, threat model.
Ship in slices. Nothing sits unmerged for a month, so you see working software early and can redirect before it gets expensive.
Deliverable Working increments, weekly, in your repo.
Tests, threat model verification, failure modes, and observability. We try to break it on purpose before real traffic does it for us.
Deliverable Test suite, monitoring, incident runbook.
Documented, reproducible, and yours to run. We walk your team through it until they can operate and extend it without us.
Deliverable Docs, walkthrough, full ownership.
05 / Stack — what we build on
We pick boring, well-understood tools by default and reach for something exotic only when the problem genuinely demands it. Here's the full picture.
06 / Engagements — how we work together
07 / Contact — start here
A system that needs building — or a manual process that shouldn't be manual? Answer three questions and we'll have the shape of it before we even talk.
Direct — Ae.th.ry.on.ex.is@proton.me
Open for work
Tell us the shape of it — services, stage, and what you're trying to do. You'll get a plan, not a sales call.
