You have an idea, or something already built. We put it on our own hardware in Prague and keep it running — the database, the files, the mail, the address, the certificate, the backups. You never assemble a stack, and you never hold five vendors together.
Prague · own datacenters · EU jurisdiction · founded 2014
2014
Trading sinceCzech commercial register · checked
Czech Republic
Jurisdiction and billing entityCzech commercial register
The part nobody quotes you for
A prototype platform puts your first version online in an afternoon. What it will not do is be the company that runs your product. We counted around 20 outside services on our own product before we moved it — each one an account, an invoice, and somebody's night.
You wanted to build a product, not become an infrastructure department.
Twenty vendors
Database here, files there, mail somewhere else, auth from a fourth company. Twenty accounts, twenty invoices, twenty jurisdictions.
Twenty things that can break
Each integration fails on its own schedule, and you find out from your users.
You cannot see any of it
Where does your data physically live? Who else can reach it? On most prototype stacks there is no answer.
What arrives with it
Everything around your project, already standing
You bring one thing. This is what we put around it before you ever see a bill — not a menu to pick from, and not extras on the invoice. It is also, word for word, the plan our intake answers with.
Your project
a repository, a prototype, or two paragraphs about what it should do
stood up when your project asks for it
Your dataPostgreSQL 18, on our cluster
Files and mediaS3 storage, our disks
Work that runs on a schedulea job runner
Accounts and sign-infor the people who use the product
Mail the product sendsa relay, and someone who watches whether it arrives
comes with every project
Your address, with its certificateissued and renewed for you
Private access for your teamadmin panels off the public internet
Backupsnightly, and the restore is tested
not built yet — today a person watches this, and we would rather say so than draw a box
Monitoring and alertsbeing built
How it starts
You hand over the project
A repository, a prototype someone built for you, or two paragraphs about what it should do. No technical brief required — and you do not have to be the one who writes it.
Our engineers stand it up
People do this, not a button — which is why it arrives working, rather than arriving as your problem. Days, not months.
It runs, and we answer for it
One bill, one number to call, and the engineers who built it are the ones who pick up.
Or hand the whole thing to your agent
You may not be the one who writes it down. Whichever coding agent you already work with — ChatGPT, Claude, Gemini, it does not matter — can describe your project in one file and send it to us. That is the entire interface: a single file in your own repository, written in your words rather than ours.
relcom.yaml
project: koalanest
contact: [email protected]
about: Booking for a dozen cabins in the Beskydy, and the owners who run them.
repo: github.com/anna/koalanest
domain: koalanest.cz
needs:
data: yes # bookings, cabins, owners
files: yes # photographs of the cabins
users: yes # owners sign in, guests do not
mail: yes # confirmations and reminders
jobs: nightly # release unpaid holds overnight
scale:
people: 500
storage: 50 GB
promote:
audience: Czech Republic, Germany, Poland
languages: [cs, de, pl]
tasks: 8 # promotion tasks a month
Fifteen fields in all, and only the first two are required. No panel to learn and no switches to get wrong. What comes back is a plan — the list above, filled in for your project, with the reason each line is or is not yours.
Today a person here reads that file and answers the same day.
And it gets found
Running is half of it. A product nobody arrives at is a product nobody bought — so the work of being found is part of the service, not a separate invoice from a separate agency. It is counted in tasks: so many a month, by plan.
What it costs
A fixed price to set it up, quoted before any work starts, and a monthly bill after that. Send the project and both numbers come back before anyone touches anything. What is in each plan is on the pricing page.
The plan prices are not published yet. They are being finalised, and a number here would be one we might not invoice — so this page says so rather than guess.
The product this company sells started as our own problem. The write-up — the stack, how many outside services, the bill before and after, and what turned out harder than it looked — is being put together with the engineers who did it, and goes out with the numbers or not at all.
A platform for AI characters with long-term memory and a personality of their own. An avatar remembers the context of past conversations and analyses the relationship; a forecast engine built on game theory — potential games, equilibrium solvers, instability signals — predicts where a pair is heading. Seven specialised assistants in an event-driven architecture.
A platform of mindful online courses, consultations and live sessions about intimacy, femininity and relationships. Courses, booking with specialists and the participant’s own space in one account; sign-in through the accounts people already have. Three interface languages: English, Russian and German.