Hard problems, honest answers, software that ships.
Straight advice, careful engineering, and a real interest in what you’re trying to achieve. That’s how we deliver software that pays off.
What we do, and how we do it.
We advise, then we build and operate what we recommended, from the first conversation to a product in production. Sometimes that’s an application we deliver, sometimes it’s our engineers inside your team. Below are the four ways we do it.
AI systems
- Claude
- Gemini
- Mistral
- Node.js
You have work that still needs a person to read something and decide what to do. We plan it with you: we go through your processes together and decide where a large language model is worth using. Then we build the workflows and agents that take that work over, inside the systems you already use. Before you rely on one, we measure how reliable it is and what it costs to run.
Web platforms
- Next.js
- PayloadCMS
- PostgreSQL
- Stripe
You need an application in the browser, for your customers or for your own team. We plan it with you and build it, from the first concept to the finished product. We build whatever the business needs around it: content your team edits itself, payments, hosting. After launch we keep developing it and we operate it: new features, upgrades, security patches. We do the same for an application you already run.
Product development
- TypeScript
- React
- Supabase
- Kubernetes
You have a plan and too few people to build it. Or you have a team and nobody deciding what it should build next. In the first case our engineers join your team and work to your plan. In the second we step in as technical lead and own the architecture, the vendors and the decisions nobody else wants to make. Both are meant to end, and the plan and the decisions stay with you.
Identity and access
- Keycloak
- Auth0
- OIDC
- Terraform
Your product has to answer two questions about everyone who uses it: who is this, and what are they allowed to do. We build the login that answers the first, including single sign-on for your enterprise customers. We build the roles and permissions that answer the second, so they match how your business works. When the business changes, we change both on the live product, and your users notice nothing. And we keep it all running afterwards, through every provider upgrade.
What we built.
Orders written as plain emails become records the ERP accepts.
Dental industry, Germany
Orders arrive as emails written by people, in no fixed format. A large language model reads each one and writes a record the client’s ERP accepts. When it cannot, it writes nothing instead of a wrong record.
- Claude, Gemini or Mistral, chosen per task
- Built in Node.js
- Delivered through GitHub Actions
The platform left Rails, and access control moved into the database.
Logistics and transportation SaaS, Germany
We moved the platform from Ruby on Rails to Next.js on Supabase. Access control now lives in the database, not in the application, so each customer only ever sees its own data. The platform also issues ZUGFeRD invoices, the German e-invoicing standard.
- Ruby on Rails to Next.js
- Row Level Security in Supabase
- ZUGFeRD invoices
- users moved
- 3M+
- microservices
- 30+
Three million users moved from Keycloak to Auth0 across thirty microservices.
Optical retail, online and in store, Germany
We moved the users from Keycloak to Auth0 together with the client’s own engineers. More than thirty microservices came along. On the way, Keycloak on Kubernetes went from version 15 to version 24, and Auth0 events now reach AWS EventBridge through Lambda.
- Keycloak 15 to 24 on Kubernetes
- Auth0 events to EventBridge via Lambda
- Datadog, Pulumi, Terraform
“We rely on Zone2 for their exceptional technical skills and strategic insights. Their ability to align with our long-term goals has made them an indispensable partner.”
When to bring us in.
Earlier than you’d think. The first few weeks of a project, when its scope is set, decide most of what it will cost. If any of this sounds like you, that’s the moment to call.
AI systems
- You’ve got a demo that works, and you need to know what it’ll cost and how often it’ll be wrong once it runs for real.
- The data you need is in emails, PDFs and scans, and someone types it into a system by hand.
- A wrong answer would cost you money or a customer, so something has to check the model’s work.
Web platforms
- Your framework is several major versions behind, and nobody dares to start the upgrade.
- You need to start charging customers, and there’s no billing yet.
- Your marketing site and your application have become two codebases that keep drifting apart.
Product development
- You’re deciding whether to hire, promote someone, or bring in outside help.
- Your CTO or technical lead has left, and the decisions are piling up.
- Your team has grown, and the way it used to work doesn’t work anymore.
Identity and access
- You’re planning a move to or from Keycloak or Auth0, and nothing has moved yet.
- Your Keycloak is several major versions behind.
- A big customer’s contract requires single sign-on, and you don’t have it.
We don’t just build software and hand it over. We work with you from the first idea to the finished product. Along the way you know where things stand. You hear from us about progress, and about problems while they’re still small.
I care about the result. I also care about how you get there. When you talk, we listen. When something is unclear, we ask. You should never wonder what’s happening with your project, or whether anyone understood what you meant.
That’s how we work, on every project. If it sounds like what you need, write to us below.
Spas Poptchev, founder
Tell us what you’re building.
Send a note or book a call, whichever you prefer. You’ll hear from us within one business day.
Or call +359 877 277 640.
A message commits you to nothing. By sending it you confirm you’ve read the privacy policy.