What working with us actually looks like

1. First conversation

You fill in the contact form describing your environment. Within two business days, an engineer — not a salesperson — reviews what you've written and sends a reply with specific questions or a proposed scope.

If your situation isn't a fit for what we do, we'll say so in that first reply. We don't drag out conversations that aren't going anywhere.

2. Environment inventory

Before we quote anything, we understand what you're running. That means a call or written exchange covering your current setup: operating systems, databases, services, traffic patterns, backup situation, and anything you know is fragile.

This step takes between one hour and a few days depending on complexity. We don't shortcut it — pricing based on incomplete information helps neither of us.

3. Scope and price

We put together a written scope document: what we'll manage, what we won't, what's included in the monthly rate, and what would require a separate quote if it came up. You review it, ask questions, request changes.

Once you accept the scope, we set a start date and introduce you to the engineer who will be your primary contact.

4. Onboarding

Your engineer gets read access to your current environment to understand it before making any changes. We document what we find. If anything is immediately concerning — an open port, an unpatched service, a missing backup — we flag it before the onboarding is complete, not six months later.

Onboarding typically takes one to two weeks for a managed VPS, longer for private cloud setups. We don't rush it.

5. Ongoing management

Your engineer is reachable by email during agreed business hours (CET, typically 09:00–18:00 Monday to Friday). For incidents outside those hours, we have an on-call rotation. Response to critical incidents is within four hours; most are handled faster.

We send a brief monthly report covering: what was patched, what was flagged in monitoring, any planned maintenance in the next month, and the current backup status. It's a one-page summary, not a dashboard full of metrics.

If something in your environment changes — you're launching a new service, expecting a traffic spike, want to add a team member's SSH key — you tell your engineer and it gets handled.

6. Incidents

When something breaks, your engineer picks it up. You get an initial assessment within four hours — what happened, what's being done, and an estimated resolution time. We update you as the situation develops. We don't go silent until it's fixed.

After any significant incident, we write a brief post-mortem and share it with you: what happened, why, what we changed to prevent recurrence. We keep these factual and short.

7. Offboarding

Contracts are month-to-month after the initial three-month period. If you decide to leave, give us 30 days' notice. We'll prepare a full export of your configuration and data, write a handover document for whoever takes over, and stay available for two weeks of questions from your new provider.

We don't retain your data after the contract ends and we don't impose exit fees beyond the notice period.