We can't find the internet
Attempting to reconnect
Something went wrong!
Attempting to reconnect
nawal:~$ technologies/elixir
Elixir & Phoenix development services.
Elixir is our core stack — not a side experiment. We build business platforms, real-time apps and APIs on Phoenix and LiveView that stay up under load and stay cheap to run.
- ★ 5.0 on Clutch
- US-timezone senior team
- You own the code
What we build with Elixir.
Most of what we ship runs on the BEAM. Here's where it earns its keep.
01
Business platforms & internal systems
ERPs, CRMs, booking engines and back offices on Phoenix — one source of truth that handles your real workload.
02
Real-time apps with LiveView
Live dashboards, availability, notifications and collaboration — rich interactive UIs without a separate frontend team.
03
APIs & integrations
REST and GraphQL APIs that connect your platform to payments, CRMs and the tools you already run — Stripe, HubSpot, Bookeo and more.
04
Migrations onto Elixir
Move the business off WordPress, PHP or a tangle of plugins onto a platform you control — the way we did for Culinary Backstreets.
05
Performance, caching & scale
Caching, background jobs and concurrency tuning, so more customers don't mean a bigger server bill.
06
Rescues & upgrades
Stalled Phoenix projects, outdated Elixir/OTP versions, thin test coverage — we take over and stabilize existing codebases.
nawal:~$ why-elixir
Why we bet on Elixir — and why it matters to you.
-
01
It stays up.
Elixir runs on Erlang's BEAM, built for systems that can't go down. Failures are isolated and recovered automatically instead of taking the whole app with them.
-
02
It scales without the bill.
Massive concurrency on modest hardware — growth doesn't mean a linear jump in hosting and ops cost.
-
03
Fewer moving parts.
Real-time UI, background jobs and APIs live in one stack, so a small senior team ships what usually takes several.
nawal:~$ projects --stack elixir
Built with Elixir & Phoenix.
FOOD TOURS · PLATFORM MIGRATION
Culinary Backstreets
We moved their whole business platform from WordPress to Elixir — bookings with availability and caching, Bookeo and Stripe integrations, HubSpot sync, and the extra tools their team needed.
−40% editor time
Read the case study
PROPERTY MANAGEMENT · WEB + MOBILE
iRent
Owners hand their property to iRent and get a dedicated manager. Cleaning, maintenance and repairs are ordered from the app; a web back office lets the team coordinate vendors, bills and monthly reports.
200+ users in the first two months
Read the case study
RESTAURANT TECH · WEB + MOBILE
Primera Mesa
Restaurant reservations with time-slot discounts — web and mobile apps for diners, plus an admin where restaurants manage tables, guests and payments.
30 restaurants on board at launch
Read the case studynawal:~$ tools
The Elixir & Phoenix toolbox.
- Core
- Elixir · Phoenix · LiveView · OTP
- Data
- Ecto · PostgreSQL
- APIs
- REST · GraphQL (Absinthe) · Webhooks
- Jobs & real-time
- Oban · PubSub · Presence · Channels
- Quality
- ExUnit · Credo · Dialyzer
- Ops
- Releases · Docker · AWS · GCP · Telemetry
nawal:~$ engagement
Ways to work with us.
Need an engineering department, not just developers?
Fractional CTO + dedicated team
A CTO who joins your leadership conversations and a senior squad that builds. One point of accountability for architecture, timelines and delivery.
Have a defined system to build?
Fixed-price project
A free one-week discovery, then a proposal with scope, timeline and a closed price per phase. Demo every Friday; the code is yours.
Already live and need it kept healthy?
Ongoing support & evolution
Monthly support for what's in production — upgrades, monitoring, performance and the next features. Optional, never a condition.
nawal:~$ process
How we work.
Four phases. The first one is free — not as a discount, but because we won't quote a system we don't understand yet.
Discovery
We sit with the people who do the work, not just the person who called us. We map how the operation actually runs — including the workarounds nobody documented. You keep the map either way.
1 week · free
Proposal
Scope, sequence, timeline, closed price — written so you could hand it to someone else and they'd understand it. You sign it or you don't.
1 week · fixed
Build
Two-week sprints. A working demo every Friday, run by the engineer who built it. Slack and repo access from day one — you can watch commits land.
8-24 weeks
Handover
We train your team on the system they now own. Monthly support if you want it, never as a condition. The code works without us.
ongoing · optional
nawal:~$ questions
Elixir & Phoenix, answered.
We're not technical. Does it matter that it's Elixir?
Only in what you'll notice: it stays up, it's fast, and it doesn't need a big ops team. We talk outcomes — uptime, speed, cost — and handle the technology. Everything is documented and the code is yours.
Should we build a new product in Elixir?
If it involves real-time features, high concurrency, or needs to scale reliably without a big ops team, Elixir/Phoenix is an excellent fit. We'll tell you honestly if a simpler stack fits better.
Can you work on our existing Elixir codebase?
Yes — feature work, performance, upgrades, or rescuing a stalled Phoenix project. We also handle migrations onto Elixir from other stacks.
Is it hard to hire Elixir engineers later?
The community is smaller but strong, and codebases are typically cleaner and smaller than equivalents elsewhere. We also help you hire and onboard your own Elixir team.
Do you use LiveView?
Yes, heavily — Phoenix LiveView lets us ship rich, real-time UIs without a separate single-page app, which cuts complexity and cost. This very site runs on it.
nawal:~$ related
Got something that deserves to exist?
Tell us what you're trying to solve. Within 24 hours you'll have a call booked and a first read on it — no cost, no commitment, no fine print.