The place where your company data stays

I put a computer at your premises and run it — it holds the company programs and data we pick together. If there is nowhere to put one, I rent a machine for you and run it the same way.

An assistant for your documents and the links between your programs have to run somewhere. Sometimes what you already have is enough — then you do not need this page. We start here when today's place is not enough, or the data cannot leave the company.

Arrange a conversation about your case

What breaks today

Data in several places at once

Important things sit scattered across services whose rules you do not set, and every month another subscription joins them. Nobody holds the full list of what is where and who can see it.

The question that returns with every idea

Every time AI comes up, the same question does too: are we allowed to put our documents there? Without an answer the project stalls before it starts.

A backup nobody ever tested

Backups run and every indicator is green. Even so, nobody has checked whether the data can actually be restored. Only a restore test shows whether the backup is usable in the case that was tested.

What it looks like after the rollout

When it makes sense

In short

Includes
We settle where the computer should stand — at your premises or on a rented machine — and I set it up. I install open-source tools for the tasks we pick together. I make backups and prove by trying that the data can be pulled back out of them. I keep watch on whether the programs are running, and I leave a sheet of paper: what to do when something fails.
What I need from you
A spot with power and network where a computer can sit permanently — and if there is no such spot, the decision to rent a machine instead. Plus one person who knows who should have access to what.

From the decision to a running place

Four steps, in this order. The first two put the hardware in place. Only the third and fourth make it something you can rely on when things go wrong.

  1. 01

    Choosing the place

    We settle whether the hardware sits with you or is rented

    a decision with its consequences named plainly

  2. 02

    Setting up

    I install the system and the tools for the tasks we pick together

    a running place for data and applications

  3. 03

    Safeguarding

    I set up backups and test them by restoring

    a backup the data can actually be restored from in the case that was tested

  4. 04

    Checking

    I attach automatic service checks and alerts

    a signal before anyone in the company notices

When the hardware fails

It will fail eventually — that is part of the project, not an exception to it. This is why the backup is checked by an actual restore rather than a green tick: afterwards you know the result for the scenario that was tested and the measured time of that attempt. That is not a guarantee for the duration of every future failure — and it is the harder part of the work, not installing the machine.

What you get

Evidence

Role
I build and run it myself
Scope
A live system I built at the company I work for, plus my own servers with around 50 services that run continuously and are described in public
Environment
Production environment — organisation confidential; plus my own environment, documented openly on tetes.pl
Kind of evidence
Production deployment (details confidential) and ongoing practice of my own
As of
2026-08
What you can check yourself
I describe publicly how it runs at my place: how I check whether the programs are working, what a plain “does it respond?” question misses, and what came out when I really pulled the data back from a backup. You can read it before you speak to me.

What this evidence does not show

I do not give the company's name and I do not show how the technology there is put together. What you can check is the open part: my own servers, which I run the same way.

Public material

How the work runs

  1. 01

    A conversation about what will run on it

    I ask what you want to start first and which data is involved. The hardware follows from that, not the other way round. 30–45 minutes, remote, no charge.

  2. 02

    Choosing the place

    Hardware with you or a rented machine: I say plainly what each option costs, how long setting it up takes, and where your control over the data ends.

  3. 03

    Setting up

    I install the system, the tools and the backups. We start with one task, not with everything at once.

  4. 04

    Restore attempt

    We restore data from the backup and measure how long it takes. Only that counts as acceptance — not a screen saying “done”.

  5. 05

    Handover or care

    Instructions and handover, or monthly care — depending on who is to run it from here.

How I price it

Hardware or rental is a cost on your side and I show it separately from my work, so you can see what you pay to whom. My part is a fixed price, set after the conversation about what will run on it.

Common questions

Hardware on site or rented — which one?

On site: the data stays physically in the company, you set access yourself, and after the one-off purchase you pay no provider a monthly rent for that machine; the costs that remain are power, the copy kept off the device, and replacing the hardware later. The start is slower, because hardware has to be bought and connected. A rented machine: you start faster and buy nothing, but you pay continuously, and the data sits with someone whose rules you do not set. By default I propose the computer at your premises, because that is why you are here: so the data stays in the company. I propose the rented machine when there is nowhere to put a computer, or you want to start right away — and I say plainly what you give up.

Do I need expensive hardware?

Usually not to begin with. One small machine covers the first tasks. AI models running locally may need a stronger graphics card, and I say so before the purchase, not after. Hardware follows the task, not a stock of spare capacity.

What if the hardware fails?

It will eventually, and that is planned for. This is why the backup is checked by an actual restore: you then know the result for the scenario that was tested and the measured time of that attempt, not a guarantee for the duration of every future failure. Without that attempt a backup is only an assumption — and it is the most common thing I find when somebody says they have backups.

Do I need a server room?

No. A spot with power and network is enough, where a device can sit continuously and nobody switches it off or moves it. If there is no such spot, the rented machine is the sounder option — and that is what I will advise.

What is not included?

I do not rebuild your network and I do not replace your staff's computers. I do not buy hardware in your name — you buy it yourself, and I say what and why. And I do not rule on whether you comply with the regulations.

Who is answerable for the data?

I answer for keeping the machine running, for testing the backups and for setting up access the way we agreed. What is in the data, and who should see it, is your company's call. Whether your case needs further formal steps is a question for your own adviser — I do the technical part and say where it ends.

Can this be funded?

In Bavaria the Digitalbonus is running; I describe its conditions on the home page. One thing worth knowing early: only a project that has not yet started can be funded, so the conversation about funding belongs before the start, not halfway through.

Let us talk about what will run on it

Write what you want to start first and whether your company data may leave the premises. I will reply with which option makes sense for you — including when I think none does for now.

Form data is used solely to answer your inquiry (details: Privacy).