Fryga — we ship on Fridays Kraków / Oslo / remote Currently booking: Q3 2026

We're the problem
to your solutions.

Most software gets shipped, celebrated, and quietly fails the person it was built for. We work with founders who refuse to call that a win.

Interlude

The format follows the problem, not the other way around.

We don't sell packages. The work changes with what each client needs: unblocking a Rails product that has stopped shipping, scaling one that's outgrowing its architecture, making AI actually stick inside a team that keeps bouncing off it, or stepping in to show a team how to do what we do and handing it back. Often some combination.

01 Case studies

Three things founders kept telling us. Three stories of what we did each time.

The format follows the problem, not the other way around. Details available under NDA.

— 01
"We can't ship. Something's broken."
Domestika · 11 months
RailsStimulusTypeScript
Problem A 13-year Rails monolith, mid-restructure, nothing moving.
Decision We decided what stays and what dies. Killed react-on-rails, rebuilt the Community module, shipped a contest platform on the new foundation.
−40% deploy time
Community module rebuilt · contest platform shipped
— 02
"We need to scale this."
FastTravel · 4 years, ongoing
RailsHotwire NativePayments
Problem One airport kiosk that had become infrastructure. Needed to scale from a single terminal to a country.
Decision Take it nationwide ourselves: barriers, cameras, chips, GPS, payments. End-to-end. We're still there.
4h → 30min driver wait
Every major airport in Norway
— 03
"AI isn't sticking."
nerds.family · ongoing
RailsAI harnessPlatform
Problem No dev team, no budget for one. Seven AI coding tools tried, none of them stuck.
Decision Built our own system from what survived, and shipped a full platform rework with two part-timers.
5+ mo AI in prod
Academy types: 1 → 3 · more output per week than a full-time dev before
02 How we work

One problem. One team. From first call to last deploy.

Most product teams are full of people doing their job exactly right. Designers protect the experience, engineers protect the code, business protects the numbers. Each one is right — and yet somewhere between all those right decisions, the product quietly stops helping the person it was built for. We close that gap by owning the whole thing.

— 01

One call.

You tell us what's broken. We ask questions until we understand what's actually going on. If we're not the right fit, we'll say so.

— 02

A sprint plan.

Scope, price, and what ships are all agreed before we start. Two weeks per sprint. No surprises.

— 03

The work.

Direct access to whoever's doing it. No standups to schedule, no project managers in the middle. At the end of two weeks, something ships.

— 04

Your call.

Continue, pivot, or stop. Everything we build is yours. The work earns the next sprint, not a contract.

03 What we won't do

If that's what you need, we'll save you the call.

We don't sell packages. The format follows the problem.
Here's what it never looks like.
MVPs

If you're starting from scratch, we're not the right call.

Staff augmentation

If you need bodies, hire full-time. It's cheaper, and they'll learn your business.

RFPs & lowest-bid

We don't compete in a spreadsheet.

Negotiating down

…and then quietly resenting the project. Either the price is right or we don't take the work.

Building whatever you spec

…without pushing back. If the feature is wrong, we'll say so.

Stack migrations

To whatever framework is trending this quarter. We pick technology by what survives, not what's loud.

04 Now booking · 2 slots available

Does any of this sound like where you are right now?

Let's talk. If we're not the right team, we'll say so on the first call. If we are, you'll have a sprint plan from us inside a week.

— Located
Kraków · the work happens wherever you are
— Currently booking
Q3 2026 · 2 slots available
— Reply time
Within 2 business days · from a real person
05 What we believe

A product is worth building only if it makes someone's life measurably better.

Anything else is just code that runs. Most teams ship the wrong thing for the right reasons — designers protect the experience, engineers protect the code, business protects the numbers. That gap between good intentions and the right outcome is the one we exist to close.

We work in small teams because quality grows where everyone feels the product is theirs. We tell each other the truth, even when it's uncomfortable. We share what we learn through writing, teaching, and open source — the knowledge isn't ours to hoard. We don't preach any of this. We just work this way.

— Teams
Small. Owned.
— Decisions
Best argument wins. Not the loudest.
— Craft
Simplicity beats clever.
fryga.io
Fryga · Kraków, Poland. We build with companies in Spain, Norway, the US, and beyond.
Marcin writes about Rails and AI at rubyonai.com
Rails conventions in the open at github.com/superpowers-rails
[email protected]
RubyPL sp. z o. o.; ul. Będzińska 5 /8, 31-403 Kraków, Poland; KRS: 0001044822; NIP: 6762646011; REGON: 52575800600000