Backend engineering
Production-ready Ruby on Rails and Elixir systems, from a focused new service to the critical core of an established product.
- Ruby on Rails
- Elixir / Phoenix
- PostgreSQL
Software that stays clear as it grows.
Alonvik helps teams build, modernise and scale business-critical backends in Ruby and Elixir—without unnecessary complexity.
Senior backend expertise,
where it matters most.
Bring in an experienced engineer for the work that needs clear thinking and careful execution—not more layers of process.
Modernisation & migration
Untangle a legacy codebase, move without losing momentum, and improve the system in steps your team can understand and own.
- Architecture
- Legacy systems
- Rails → Elixir
APIs & data-intensive systems
Reliable integrations, data pipelines and APIs designed for real traffic—observable, maintainable and calm under pressure.
- API design
- Data pipelines
- Performance
Technical direction
Senior hands-on support for architecture decisions, delivery practices and teams that need an experienced outside perspective.
- Technical review
- Mentoring
- Delivery
Proof lives in
production.
Alonvik is led by Joakim Nylén, a backend developer, founder and consultant with more than fifteen years in software. The common thread is making complicated systems dependable.
More about the work
Independent by design
One senior partner, directly involved from architecture to shipped code.
Outdoor platforms at Nordic scale
Architecture and development for systems serving millions of daily views, including a careful Rails-to-Elixir migration.
Time-sensitive data, delivered reliably
High-volume pipelines that collect, normalise and deliver information to Swedish media companies around the clock.
Senior capacity inside the team
Hands-on engineering and knowledge transfer that move difficult product work forward without adding ceremony.
Close to the code.
Close to the outcome.
Good consulting leaves you with more than shipped code. It gives your team better options, fewer surprises, and a system they can keep evolving.
- Step 1
Understand
Start with the product, the people, and the system as it actually is.
- Step 2
Make it clear
Turn complexity into decisions, useful milestones, and honest trade-offs.
- Step 3
Build together
Ship production code, share context, and leave capability behind.
A few things clients often ask.
A little context on how Alonvik works with Ruby, Elixir and business-critical backend systems.
Yes. Alonvik works hands-on with Ruby on Rails and Elixir/Phoenix, including PostgreSQL, APIs, background processing and production operations. The right choice depends on the system, the team and the problem—not a technology preference.
Yes. Most engagements happen inside an existing product team. Alonvik can take ownership of a difficult area, add senior delivery capacity, review architecture and share context without introducing unnecessary process.
Yes. Migration work is approached incrementally, with production stability and continued product delivery as constraints. That can mean extracting selected capabilities, clarifying boundaries or moving workloads in stages rather than attempting a risky rewrite.
Typical work includes business-critical web platforms, high-traffic APIs, data pipelines, integrations and systems that have become difficult to change safely. Reliability, observability and maintainability are treated as product concerns.
Hands-on. Architecture and technical direction are backed by production code, tests, reviews and delivery. The aim is to solve the immediate problem while leaving the team with clearer options and stronger ownership.
It starts with a focused conversation about the product, system and current constraint. From there, Alonvik can join as an embedded specialist, lead a defined project or carry out a technical review with practical next steps.
Have a hard
backend problem?
A few lines about the system, the situation, and where you want to go are enough to start. No pitch deck required.