Service
Infrastructure
We arrange the place your services live in: a Linux server, Docker containers, Nextcloud for files, a local language model on a separate machine, a link to the edge devices — with no open door to the whole internet.
Who it is for
A team growing out of one computer under a desk, or a fleet that needs a steady server.
What it covers
- A Linux server and Docker for the services we run
- Nextcloud as a private file cloud
- A local language model on its own machine
- A path to the edge devices without opening a door to the whole internet
What you get
- Data has an address, not “somewhere in the cloud”
- Services start in a repeatable way, not from memory
- Machines do not depend on an open internet port without a reason
How we do it
We do not start from a catalogue of fashionable cloud names, but from the question of where data must live and who touches it at night, when the machine is selling and the office is closed. If you do not want hardware in the office — it stays with us; if you want it at your site — we come and raise it there. Services start repeatably, not by hand from memory.
And everything is handed over with a note: how to log in, where the copy is, what not to touch, and whom to call. Without that note, commissioning is not done.
How an engagement runs
01. Boundaries
Which data is sensitive and where it is allowed to live.
02. Sketch
Server, network, and services on one page.
03. Bring-up
Installation and the first real login.
04. Note
How to restart, where the copy is, and whom to call.
Questions on this topic
Do you only offer a cloud?
No. Often the machine is at your site. Hosting with us is the option when you do not want hardware in the office.
Does the local model belong here?
Yes, as part of the infrastructure. The Local AI service page describes the assistant itself.