Systems & data
Concurrency, fault tolerance, and the data model everything else sits on. The person who decides how a system behaves on its worst day, not its best.
Elixir, OTP, Ash, Oban, Postgres
00 The studio
Three engineers. No org chart.
We are not a company that grew a management layer. We are three senior engineers who kept building, took on the work we believed in, and answer for it ourselves.
Start a projectWhy we exist
- 01 Software here is usually sold by people who will never open the codebase
- 02 Work gets won by a senior and delivered by whoever was free
- 03 The team disappears the week after launch, when the real problems start
- 04 Nobody is accountable when a system stops holding up two years in
↓
We built the studio we would want to hire: the people who scope your project are the people who write it, and they are still there in year two.
Who you work with
Three founders, equal sayWe do not publish titles. Titles describe a hierarchy, and there is not one here — every founder owns a domain, holds the final say inside it, and writes production code every week.
Product & interface
How the software looks, feels, and holds together as it grows. Designs the interface and builds it — not a handoff between two people who never speak.
SvelteKit, Next.js, TypeScript, design systems
Infrastructure & delivery
Where the software runs and how it gets there. Makes releases routine and failures visible, so nobody finds out from a customer.
Cloudflare, Terraform, CI/CD, observability
How we work
You talk to the builders
No account manager, no relay. The person answering your question is the one who wrote the code it is about.
We ship to your deadline, not ours
A month or a year — the timeline follows what you actually need. An MVP or a first working version does not sit in discovery for a quarter; it goes live and starts earning feedback.
Nothing merges unreviewed
Every change is read by another founder before it ships. Reviews check the approach first, style second.
We say no
If a project is not a fit — wrong stack, wrong timeline, wrong problem for us — we say so rather than take the work and learn on your budget.
We stay with it
Everything is yours — your repositories, your cloud accounts, your data. We hold nothing hostage, and we keep maintaining and improving it long after launch.
What we believe
Boring technology, chosen deliberately
We use Elixir, Phoenix, SvelteKit and Terraform because they are documented, hireable, and proven — not because they are new.
The second year is the test
Anything can be made to work for a demo. What matters is whether it can still be changed safely once the people who built it have moved on.
Scale is a design decision
Systems do not become scalable later. Either concurrency and failure were designed in from the first line, or the fix is a rewrite.
Small and senior beats large and layered
Three people who all write code move faster than a team where most of the headcount exists to coordinate the rest.
Where we are
Based in Morocco, working remotely with clients wherever they are. We work in English, French and Arabic — the same three languages we build software in.
Now tell us about yours.
A short call, an honest answer on whether we are the right team, and a scope you can budget against.
Start a project hello@elixiria.ma