Nobody notices when something goes down.
Until the first customer calls.
Photo: Taylor Vick / Unsplash
Building it isn't running it.
You built it.
We keep it running.
RunTheThing takes over the operation of software that was built with AI – whether it's an app, a customer portal, an internal tool or a backend. We assess, harden, automate, run and ship.
Monitoring. Backups. Updates. And someone who picks up within the agreed service window.
Unknown code. Clear responsibility.
rtt / system_file_001
$ rtt inspect ./your-app
[01] codebase ........ FOUND
[02] dependencies .... MAPPED
[03] backups ......... UNKNOWN
[04] monitoring ...... MISSING
[05] ownership ....... UNCLEAR
→ LET'S FIGURE IT OUT.
01 / The problem
The software is running. For now.
A prototype goes live in no time. But what happens when it turns into a system people rely on?
Backups? Somewhere. Maybe.
Nobody knows whether a restore would actually work.
Updates pile up.
Dependencies age and security holes stay open.
The code is there. The knowledge isn't.
Nobody knows all the services and dependencies.
The original builder is no longer around.
Who takes care of deployments, bugs and data now?
AI can build software. But someone has to run it tomorrow.
02 / What we do
Five building blocks.
One goal: it runs.
You start with the Operations Check. Then you decide what you handle in-house and what we take over.
01 / IDENTIFY
Understand
The Operations Check: we review code, infrastructure, access, dependencies, security, monitoring and backups. No sugarcoating.
Result: A case file with a traffic-light rating and an action plan. Fixed price from €990.
02 / HARDEN
Harden
We close the critical gaps: access, secrets, deployments, backups with restore tests, monitoring and logging.
Result: A production-ready application with a runbook.
03 / GUARD
Automate
You keep building with AI, we build the guardrails: every change is tested and checked automatically before it goes live.
Result: A CI/CD pipeline with approvals and a way back.
04 / RUN
Run
We monitor and maintain the application, install updates and respond to incidents according to agreed rules.
Result: Managed operations for a monthly flat fee from €149.
05 / SHIP
Ship
Releases for the web and the app stores: versioned, tested, rolled out in the agreed window.
Result: Everyone who is supposed to use it can get in and get to work.
03 / System file
Unknown code.
Clear responsibility.
We find out what's running. And what it needs to keep running.
RTT / SYSTEM FILE 001STATUS: UNKNOWN
UNKNOWN → IDENTIFIED → OPERATIONALRTT_
04 / Who it's for
You have the software.
But no ops team?
▦
SMEs & mid-sized companies
Internal tools, portals and reports – often built with AI, long since indispensable.
Why RTT? →✳
AI builders & founders
A quick MVP has turned into a product with real users.
Why RTT? →↗
Agencies & consultants
You built something fast for clients and don't want to carry its operation forever.
Why RTT? →⌘
Education providers & associations
Home-grown admin tools and learning platforms without a clear owner for operations.
Why RTT? →CH_
ENGINEERING / RESPONSIBILITY
05 / Who's behind it
No magic.
Operations.
I'm convinced: you have to understand what you run – no matter whether a person or an AI built it.
I have been developing and running software and infrastructure since 2005. I know how quickly an application comes together – and how much experience it takes to make it work reliably day to day.
With RunTheThing, I take care of exactly that part: understanding, hardening and running. Without unnecessary complexity and without promises that don't hold up when it matters.
Christian Heimke
RunTheThing · A brand of Loumaris UG (haftungsbeschränkt)
Responsibility also means knowing your limits.
We don't take on every system. And on-call coverage, backup staff and response times are only promised once they are reliably organized for the specific system.
06 / How we work
No black box.
A clear process.
01 / REQUEST
Talk first
What's running? Where? For whom? How critical is it?
02 / REVIEW
Operations Check
Understand the technology and the risks before we take on responsibility.
03 / HARDEN
Close the gaps
Plan and implement the necessary measures.
04 / RUN
Set clear rules
Put services, response times and responsibilities in writing.
07 / Frequently asked questions
Good questions.
Clear answers.
Do you run any kind of software?
No. We first review the architecture, stack, security and risks. We only take over a system if that is technically and organizationally sound.
Does the application have to be built with AI?
No. Conventional or organically grown systems qualify too. What matters is whether we can take reliable responsibility for running them.
Does the software have to move to you?
Not necessarily. We review the existing environment and agree together on which infrastructure makes sense and can be operated.
Do you develop the application further?
Targeted changes are possible by agreement. Open-ended further development is not part of an operations contract.
What happens during an outage?
That depends on the agreed service level. We define availability, on-call coverage, backup staff and response times bindingly before we take over operations.
What does it cost?
The Operations Check starts at €990 net as a fixed price. Ongoing operations start at €149 per system per month. All prices are on the pricing page.
08 / Next step
Is your software running?
Or just running for now?
We review where your application stands – and what's missing for well-organized operations.
Or email us directly: kontakt@runthething.de
Understand first, then decide. No automatic takeover of operations.