A studio with a real point of view, and the scars to back it.
We’ve spent years building and scaling software inside other people’s companies, the payments that can’t drop a transaction, the pipelines that move millions of events, the rebuilds nobody wanted to touch. Panal brings that experience straight to you, without an agency layer in between.
We stay small on purpose. It means the people you email are the ones writing the code, and the ones who’ll tell you, before you spend a cent, if the exciting idea is the wrong one for right now.
actually talk to
“I started Panal because I kept watching good projects fail for the same reason, not bad code, but a builder who reached for the exciting tool instead of the right one. There’s no one-fits-all in software; the problem in front of you decides everything, and the best solution on paper is rarely the right one today. So I don’t start with a stack. I start with your real constraints, the budget, the deadline, the team you actually have, and what happens at 3am when something breaks, and I build backwards from there. Sometimes that means a distributed system built to absorb real load; just as often it means the boring thing that fits and never falls over. My vision is simple: software that’s the right size for its problem, nothing wasted, and still standing long after I’ve gone.”
Who you’ll actually work with.
Visal Hettiarachchi
Chamuth Chamandana
A panal is a honeycomb, the most efficient structure in nature. Hexagonal cells, each one bracing the next, maximum strength for minimum material, nothing wasted. It’s not the most elaborate thing bees could build. It’s the right one. That’s the whole idea: the right structure for the problem in front of you, and not one cell more.
Panal is young, and we’re not going to pretend otherwise. We’d rather earn your trust with how we think than with a wall of logos. If the thinking fits your problem, the rest follows.
What we won’t compromise on
The right tool, not our favourite one
We have preferences. They don't get a vote when they're wrong for your problem. The comb bends to the job, not the other way round.
Boring on purpose
Proven, unfashionable tools used exceptionally well. We save the clever stuff for the two percent of a project that actually needs it.
Say the awkward thing
If the deadline is fantasy or the feature is a mistake, you'll hear it from us early, when it's still cheap to change course.
Own the outcome
We measure ourselves by what ships and holds up in production, not by hours logged or tickets closed. Working software, or it didn’t happen.
Small and deliberate
A few projects at a time. No bench of juniors learning on your budget, no work handed off to whoever’s free.
Leave it better than we found it
When we hand back a system, your own team should be glad to own it, long after we’ve moved on to someone else’s hard problem.