Private infrastructure and maintenance.
I prepare a private environment for your software, deploy the applications you already have and set up who can get in, how to spot problems and how to recover the data.
You can hire me for infrastructure, deployment or maintenance alone. You do not need new software built. Ongoing maintenance is optional.
- Checks
- Data backups
Get it running. Know if it fails. Be able to recover it.
We agree what your business needs and which parts I will manage before work starts.
Prepare and deploy
I organize the environment where your applications will run and make them accessible to the people who need to use them.
- A private server for an existing application.
- Deployment of the application and its database.
- Restricted administration access and HTTPS.
Detect and recover
I set up checks, alerts and data backups. A restore test checks what can be recovered and how.
- External availability checks.
- Encrypted backups away from the server.
- Restore tests for the application and its data.
Maintain, if you need it
If you want help after deployment, we agree a maintenance service to review the environment and handle the changes or incidents included in its scope.
- Review of alerts, backups and access.
- Planned and tested updates.
- Written responsibilities and coverage.
What you can hire me for.
You already have an application
You need to deploy it in a private environment and know who will look after its access, backups and maintenance.
You already have a server
You need to review how it is organized, which services are accessible and whether its backups can recover the application.
You want to keep your developer
Your team builds the software. I can handle deployment and the environment, with responsibilities agreed between everyone involved.
How we work.
Review what you have
Tell me which applications you use, where they run and what your business needs. We review the requirements and limits of the existing software.
Agree the scope
We define what to prepare or change, who keeps access and which tests, documentation and support are included.
Prepare and check
We deploy what we agreed and check access, alerts and recovery within the scope. Results and limits are documented.
Hand over or maintain
You receive the documentation and agreed responsibilities. If you need it, we agree ongoing maintenance separately.
Scope, price, coverage, response times and recovery objectives are agreed per project. Round-the-clock support and guaranteed availability are not assumed.
Technical detail, if you need it.
For technical teams and specialist buyers: these are options we can include in the scope, depending on the application's requirements.
Environment and deployment
Virtual private server (VPS), Docker containers, deployment configuration and databases. We review compatibility, resources, persistence and the procedure for publishing changes. DevOps work is limited to the agreed scope for your environment.
Access and exposure
Private administration, restricted accounts and permissions, key-based access, network rules and HTTPS. We agree what must be public and what only authorized people can reach, with exposure checks where included.
Monitoring and alerts
Checks from outside the server, service status and incident alerts. We define what is checked, who receives alerts and who acts; an alert alone does not mean round-the-clock support.
Backups and recovery
Encrypted off-site backups for included data and volumes, a retention policy and recovery access. Restore tests run in an isolated environment and document what was recovered. Any complete server rebuild is scoped separately.
Maintenance and handover
Environment inventory and documentation, agreed custody of access, reviews and planned updates. Coverage, hours, response times and responsibilities are defined in writing. Not every application or update is covered automatically.
Own infrastructure, with evidence and limits.
The OpsByFabian internal platform case shows the work and validation documented in September 2026. It is an owned technical reference; it is not presented as a client's environment.
Scope A: on 8 October 2026, 44 Core + Automation technical checks were accepted on one blank test server. This acceptance excludes Hermes and Scope B/Full; historical September tests do not extend it. It does not validate every component or future version. Each client environment needs its own tests and acceptance; this is not a universal guarantee.
See the historical September caseWhat do you need to run or maintain?
Tell me which application or environment you have and what you need to solve. We talk directly, including if you only need infrastructure and maintenance.