Skip to main content
Techlogia — AI and Web Development Berlin

IT support and systems-house work in Berlin.

Most outages announce themselves, only nobody is listening: a certificate close to expiry, a backup running empty for weeks, a service that does not come back after a restart. Support here means those things get noticed before they cost a working day.

No hardware resale, no round-the-clock field service. One contact instead.

When someone has to stand at the machine, the drive is short

Most support happens over secured remote access and needs nobody in the room. What does need it, needs it urgently: a machine that will not start, a replacement, a handover. From Berlin-Wedding that is a drive, not a travel day — and that is the real difference from a provider three federal states away.

Techlogia — Jaciel A. Acea Ruiz
Prinzenallee 38
13359 Berlin

Who we support

Small businesses, associations and practices in Berlin and Brandenburg with a manageable number of servers and workstations. Pure remote support is possible across Germany, as long as on-site work is not part of the commitment.

Four things that must run so the rest can run

Support is not a maintenance contract where someone clicks something once a quarter. It is four tasks that have to be permanently done — and whose absence only becomes visible on the day of the outage.

01

Setting up and hardening servers

Base installation, firewall, key-only access, automatic security updates, separate users per service. Documented traceably, so the knowledge does not sit in one person's head.

02

Monitoring with an alert that arrives

A detector that stays silent looks like calm. So every monitoring setup includes a test of whether the alert path actually works, and a second path in case the first fails.

03

Backups with a rehearsed restore

A backup only becomes one once it has been restored. Encrypted, on separate storage, with a way back that is written down and rehearsed regularly — not first attempted on the day of the outage.

04

Planning the network instead of letting it grow

Separate areas for administration, workstations and guests instead of everything in one network. Secured outside access for administration. Planning comes before drilling — fixing afterwards costs more in both trades.

How support begins

  1. 01

    Inventory

    What runs, what is reachable from outside, what is backed up and what is not. You get the result in writing — even if you decide not to continue with us afterwards.

  2. 02

    The urgent things first

    The inventory becomes an order of work ranked by potential damage, not by effort. A missing backup comes before an untidy configuration, even though the second would be fixed faster.

  3. 03

    Set up and document

    Every change is recorded as a procedure: what was decided, why, and how to get back. Those documents are yours, and they are the reason a change of provider stays possible later.

  4. 04

    Ongoing operation

    Updates, monitoring, backups and an agreed way to reach us. Response time is set in advance and not negotiated during an incident.

What the price depends on

Ongoing support cannot sensibly be reduced to a single figure before it is known what is being supported. These four factors determine it — and after the inventory there is a fixed monthly amount, not an hour account that grows during an incident.

Number of systems
Two servers and five workstations are a different matter from three locations. What counts is what should be monitored, updated and backed up — not what happens to be standing around.
Agreed response time
Whether an incident is picked up the same working day or within a few hours is the single biggest lever. Short times mean standby, and standby costs whether or not anything happens.
Remote or on site
Pure remote support is the normal case and the cheaper route. Committed on-site visits are possible but belong explicitly in the agreement, rather than becoming a point of dispute case by case.
Condition at the start
A well-kept environment costs less to support than one where the basics have to be caught up first. The inventory says which it is — and it says so before the contract, not after.

Net, plus VAT. The inventory is a self-contained piece of work with its own price and commits you to nothing. One-off work such as setting up a server is priced from the packages in the service catalogue.

What sits behind it technically — which stack is operated, how monitoring and backups are built, and where the boundary to a licensed electrician runs — is on the service page.

See IT infrastructure & networking

Frequently asked

Questions we get asked a lot

Are you a systems house?

Not in the classic sense, and that deserves saying plainly: there is no hardware resale, no round-the-clock field service and no phone systems. What there is: setting up, hardening, monitoring and maintaining servers, networks and backups — by one person you speak to directly.

Do you take over systems someone else set up?

Yes, and the first step is always an inventory: what runs, what is reachable from outside, what is backed up and what is not. You get the result in writing — even if you decide not to continue with us afterwards.

How quickly can we reach you, and do you come on site?

Most of the work happens over secured remote access and needs no travel. In Berlin and the surrounding area, on-site appointments are possible when someone genuinely has to stand at the machine. Response times are agreed up front, not negotiated during an outage.

What if we want to change providers?

Then you can. Every setup is documented as a traceable procedure — what was decided, why, and how to get back. Those documents are yours. Someone else being able to take over is intentional, not an oversight.

Have a project?

Let's bring your idea to life together. We're happy to advise you with no obligation.

How do you like this page?