Infrastructure agentization
One gateway in front of every model, a key per project, a budget per project, an audit log. Then agents that read freely and write only on confirmation. The kind that notices the disk is filling up.
More →The Future is Already Here …it’s just not very evenly distributed (William Gibson)
…it’s just not very evenly distributed (William Gibson)
It runs here. Agents operate our infrastructure, and the applications we built are the ones we use every day. Sensitive data has a boundary it does not cross. We only sell what we run on ourselves first.
Twenty-five years keeping production systems alive. Agents now run part of ours — and we know exactly where they can be trusted and where they cannot.
Four things, done properly
One person does the work. That is why the list is short — and why it holds only what we can actually deliver alongside the work we already carry.
The software you are missing
An application that does one thing and has an agreed end date. You get it with the source, and then it is yours. We run several ourselves and use them daily, so we can also tell you what breaks on them a year in.
More →AI enablement for your teams
Your people already use AI. The question is whether they use it well and whether you can see it. A day on site, on your real workflows and on agentic tasks. We work, we do not lecture.
More →Home automation
Home Assistant deployed through its API as code — reviewable, revertable, rebuildable. It survives the vendor rewriting their API. Households or offices — the same engineering either way.
More →References
Who we have already worked for
- SME.sk (opens in a new tab)
- Innovatrics (opens in a new tab)
- Safety Line (opens in a new tab)
- Herbárium Projekt (opens in a new tab)
A short list, and it is meant to be. What exactly we did for whom we will happily tell you in person — some of it is the client's to disclose, not ours.
The question everyone actually asks
Where does our data go?
Aggregates go to the cloud model. Anything sensitive — raw records, identifiers, location, health data — never leaves the network. It runs on a local model, on your hardware. This is not a promise on a slide; it is the boundary we run our own systems on, because some of our own data is the kind you do not hand to anyone.
What that looks like in practice
70 rules, 44 on backups
one alert rule per backup job, each with a threshold matched to its own schedule. A backup nobody checks is a work of fiction.
20 routes, 1 gateway
every model behind one door, a key per project, a budget per project. Swapping provider is a one-line change in the gateway.
Seconds of downtime
router, DNS, DHCP and VPN migrated while everything kept running. The only outage was the few seconds it took to move a cable — there was no way around that one.
No NOC
our own server at our premises, a standby in another town, a rented one in the cloud. Alerts arrive in Signal — because the first responder is an agent.
These numbers come from our own infrastructure and are verified as of the date in the footer. Not a client list — a lab. It is where we test what we would propose to you, and it is why we can show you the scars instead of the slides.
Five things we built and run
Every one of them is ours, in production, and still running this morning.
Custom software · in production
Applications we have to live with
An accounting system that pulls its own bank statements. A PWA for a festival with no signal. An app that sells on Bazos. A health-data backend behind a VPN. Each came out of a problem of our own — and because we use them daily, we know what breaks on them.
Monitoring · built from zero
Monitoring you can actually trust at 3 a.m.
Seventy alert rules over everything we run: hosts, containers, disks, GPU temperature, days until a certificate expires — and forty-four of them watch the backups. Above it a status page that answers the question “is it all up?” in three seconds from a phone.
Backups · measured
Backups that survive an attacker with root
An offsite receiver in another town, reachable only over WireGuard and running append-only: a compromised server cannot rewrite or delete backup history. Ten jobs, GFS retention, each with its own alert rule.
Start with an hour
No deck, no discovery workshop, no invoice. One hour, and you will get a straight answer: this is what we would do, this is what it costs — or, you do not need us for this.