Build, don't license
We build the software your company runs on.
Belgian and founder-led. We start by measuring what IT costs and where your processes stall, then replace scattered tools and per-user licences with one open-source platform on EU cloud, the code in your own repository from day one. In waves, with a go or no-go at every step.
Day 1
code in your repository, no lock-in
90 days
first working result
0 licences
growth costs infrastructure, not users
From audit to migration, in four steps
We start with an audit that exposes the cost, the process and the risks. First we optimise the process, because software on a messy process only makes the mess faster. Then we build and migrate in waves on an EU cloud, with the code in your ownership.
Audit
Cost, process and security mapped out. A baseline your finance team co-signs.
Optimise
The process first: steps removed, duplicate work gone. Often a gain without new software.
Build
One platform in waves on EU cloud, with the code in your ownership.
Migrate
Phased from your old systems. Legacy keeps running until every wave is stable.
One platform, value for every role
Management, IT, operations and finance each look at software differently. One platform answers all four at once.
You decide at each gate, no lock-in
Every build wave ends in a go or a no-go. The code is yours, and the base fee stops the moment you say no-go.
Standard open-source stack
Kubernetes, PostgreSQL, ClickHouse, Metabase. Code in your repo, transferable to any integrator, security at NIS2 level.
One environment for your daily work
Counter, stock, quotes and support in a single login. One update, all locations at once, offline where the counter needs it.
No per-user licences
Growth costs infrastructure, not users. The success fee is 20% of confirmed savings, measured against a baseline your finance team co-signs.
Built to hand over, not to lock in
Approach and method
Built in waves with gates. Legacy keeps running until every wave is stable. The same build line, components and tests in every module.
Open source and ownership
No licensing layer. The code sits in your repository from day 1, with escrow and transferable to any integrator.
Security and compliance
EU cloud, SSO and MFA, WAF, audit trail and daily back-ups. NIS2-level controls, regardless of the formal scope.
The difference
What you get that a licence model does not
| Kostenlijn | Licentiemodel | Met YK |
|---|---|---|
| Software licences | Per user, annually | No per-user licences |
| Cost of growth | More users, more licences | Infrastructure, not licences |
| Code ownership | With the vendor | In your repository, day 1 |
| Transferability | Vendor lock-in | Any integrator takes over |
What we build
Eighteen modules, from sales and stock to HR and dashboards. Every tile is a module, not a package. You take what you need, regardless of sector or size, on a foundation of Kubernetes, PostgreSQL, ClickHouse and Metabase.
Quotes & CRM
replaces separate sales tools
Counter & POS
offline mode for customer contact
E-commerce & webshop
online and at the counter from one stock
Customer portal
customers order, track and pay themselves
Marketing & campaigns
mailings and segments on your own data
Ticketing & support
all questions in one system
Start with an audit: cost, process or security
Pick one axis or all three. Four weeks, fixed price, vendor-neutral, and a baseline your finance team co-signs. No obligation to continue.
Transparent, no surprises
Audit report
Fixed price, one-off. A vendor-neutral report that stands on its own.
Base fee
Fixed per quarter, nothing on top of the run rate.
Success fee
20% of confirmed savings, running things twice never counts.
What management, finance and IT ask us
The questions you ask before you engage a build partner, answered honestly.
Do we end up locked into YK over time?
No. The code sits in your own repository from day 1, on a standard open-source stack that any integrator can take over. Every build wave ends in a go or a no-go, and that is a real exit point each time. If you stop, you keep the working software and the code.
Who owns the code you write?
You do. We build in your repository from the first day, there is no licensing layer or closed proprietary system in between. You read, fork and transfer the code whenever you want, without asking us for permission. Why that difference matters is explained in vendor lock-in and real ownership.
What happens at a no-go, or if we stop?
At a no-go the base fee stops and we do not start the next wave. Your legacy keeps running in the meantime, because we switch nothing off until a new wave is stable in production. You keep what has already been built and paid for, and you decide again at every point. That is how our build in waves with gates works.
What about security and NIS2?
We work at NIS2 level, regardless of the formal scope: EU cloud, SSO and MFA on your existing identity, a WAF, an audit trail and daily back-ups. Every year we run a DR test. Counter and POS have an offline mode, so the daily operation does not stall during an outage. See our cybersecurity audit and NIS2 in practice.
Where does our data sit?
In EU cloud, on infrastructure you take at public list prices. Transaction data sits in PostgreSQL, analytics in ClickHouse, both open source and transferable. There is no data lock: you can take a full export at any moment.
What about costs and licences?
There are no per-user licences. Growth costs infrastructure, not users, so more people does not automatically mean more software costs. You pay a fixed base fee per quarter and a success fee of 20% of confirmed savings, where running things twice never counts. An IT FinOps audit exposes your run rate over five years.
How quickly do we see something working?
The first working result is there within 90 days: one module in production, alongside your existing systems. We build module after module, so you see value before you commit to the next step.
What if YK falls away?
Then everything keeps running. The code sits in your repository, the stack is standard open source, and there is an escrow arrangement. Any integrator can take it over, because there is no YK-specific magic in the system.
How does this differ from a classic software vendor?
A classic vendor keeps the code and sells you licences per user, which locks you in. With us the code is yours from day 1, you pay for infrastructure instead of users, and you decide per wave whether we continue. We do not sell licences and we do not sell hardware. See why closed ERP rarely fits the mid-market.
What does the IT FinOps audit cost?
The audit has a fixed price and is one-off, with no obligation to continue. In four weeks we deliver a vendor-neutral report with a baseline your finance team co-signs, usable with or without YK. Because we sell no licences or hardware, the research is neutral. More at our audits and from audit to saving.
Build software you own, without lock-in.
Belgian, founder-led and built to hand over. One e-mail is enough.