When we demo Kaldryn One, the most common reaction isn't a question about tokens per second or context windows. It's someone pointing at the box and asking: “That's it?”
That's it. A locker-sized black appliance, quieter than the office fridge, plugged into a normal wall outlet and your network switch. Inside it: your company's entire AI capability. Chat over your own documents, more than two hundred curated open models, an OpenAI-compatible API, and not a single byte leaving the building.
The problem with “just use the cloud”
For a lot of teams, cloud AI is genuinely fine. But every conversation we had with hospitals, law firms, banks and public agencies across the Nordics followed the same arc: people were getting real value out of consumer AI tools, leadership wanted that capability properly, and every path to it ran through somebody else's infrastructure, under somebody else's terms.
- The pricing scales with headcount. Per-seat AI subscriptions are a tax on growing.
- The data leaves. However good the contract is, a prompt typed into a cloud assistant physically departs your premises.
- The dependency compounds. Models get deprecated, terms get revised, prices change, and your workflows are built on all of it.
For regulated organisations, the second point alone often ends the discussion. Our answer is not “trust us instead”. It's: don't send the data anywhere at all.
Constraints make products
We gave ourselves three constraints for the appliance, and they shaped everything:
- It has to live in an office, not a server room. That set the acoustic budget (under 38 dB, quieter than normal conversation), the power budget (a regular wall outlet, no three-phase), and the size (locker, not rack).
- An IT team of one has to run it. Two cables, power and ethernet. It arrives pre-configured, indexes your documents on-box, and serves your team the same day.
- It has to keep working with the internet unplugged. Not as a party trick, as the operating assumption. Updates are something you choose to apply, not something that happens to you.
The test we kept coming back to: if you pull the network cable out of the wall, what still works? For Kaldryn One the answer is: everything. That's the difference between owning your AI and renting it.
What “a datacenter” actually means for a 30-person firm
The phrase sounds grandiose, but look at what a small organisation actually needs from AI infrastructure: an assistant that knows its documents, a private API for the tools it builds, and governance a lawyer can sign off. That's not a hyperscale problem. It fits in a box, GPUs, storage, models, retrieval, admin console, audit log, all of it.
One box for a thirty-person firm. Racks of them for a data center. The platform is the same either way, which is exactly the point. Sovereignty shouldn't be an enterprise luxury.
What's next
We're publishing more of the thinking behind the platform here on the blog, the engineering trade-offs, what runs well on one box in 2026, and what we're hearing from the regulated side of the market. For the deeper technical material, the research hub has the reference architecture and compliance white papers. And if you'd rather just see the box: meet Kaldryn One.