Open Source & Self-Hosting

Your applications.
On your infrastructure.

I help businesses select, configure and integrate self-hosted applications. Turn an open-source tool into a usable system, with access rights, backups and updates planned from the start.

Discuss your self-hosting plans

Stefan Pilz · Linux & Docker · Remote setup and consulting

IllustrationSelf-hosting includes planning how software is operated.

SERVICE OVERVIEW

What open source and self-hosting mean for your project

Open-source consulting and self-hosting at SP Webconsulting cover the selection, evaluation, setup and agreed support of suitable applications. I work with Linux, Docker and document management solutions, considering data, permissions and ongoing operation. Whether a self-hosted application makes sense is assessed against your requirements.

This service is for companies that want greater control over data and applications or need to solve a specific task using existing infrastructure. You may have a confusing document archive, need a suitable internal application or want to compare an alternative to an existing service. Self-hosting is an option, rather than an end in itself.

Your contact: Stefan Pilz · Stefan Pilz Ltd. · Collaboration is 100% remote

SERVICE SCOPE

Select, configure and operate the right tools

Choose tools around your workflow

I compare suitable applications against your business requirements and intended use. This includes imports, search, user management, interfaces and who will maintain the system. A limited trial can establish whether a tool supports the actual workflow before larger datasets are migrated.

Set up Linux, Docker and applications

After selecting a solution, we can agree its installation, configuration and integration into your existing environment. We consider storage, access, permissions and necessary connections. Existing NAS or server hardware is assessed for suitability; its availability alone is not a reason to recommend it.

Clarify operation, backups and responsibilities

Introducing a system includes deciding how updates, backups and incidents will be handled. We agree which data will be backed up, who responds to notifications and how restoration should be tested. Ongoing support can be arranged, with a defined scope and available contacts.

POSSIBLE USE CASES

Three possible uses for self-hosted software

Example workflow

The application is only part of the system.
  1. 01
    ApplicationSelect a suitable tool
  2. 02
    AccessRoles & permissions
  3. 03
    OperationUpdates & monitoring
  4. 04
    RecoveryBackups & restore tests

An illustrative operating model. Responsibilities and security requirements are agreed before setup.

The following examples describe possible assignments, not documented client projects.

Evaluate document management with Paperless-ngx

A limited document collection is used to test imports, tagging, search and permissions. We then decide how to migrate existing files and which manual checks remain necessary.

Run an internal application in a container

A suitable tool needs to be made available in an existing environment. We review the prerequisites, configure the application and document its data storage, settings and planned update process.

Compare self-hosting with a managed service

A company wants to operate an application it currently buys as a service. The comparison considers functionality and control of data alongside hardware, maintenance, backups and the effort involved in resolving incidents.

DELIVERABLES & SCOPE

Your setup and the responsibilities involved

Your agreed deliverables

We agree the deliverables before starting. Depending on the scope, these may include:

  • A justified selection or assessment of suitable applications for the agreed use
  • A test installation or configured application with agreed settings
  • Documented access arrangements, roles and responsibilities without publicly exposed credentials
  • An agreed approach to updates, backups, restoration testing and ongoing support

What we clarify beforehand

Open source does not automatically mean free or maintenance-free operation. Hardware, setup and ongoing responsibility still matter. Availability, recovery or confidentiality requirements may rule out a particular setup. Physical installation and work on site are not part of my remote service.

Effort and costs

For an initial assessment, describe the intended use, approximate number of users, available equipment and the type of data involved. We agree remote access and local contacts later in the process. Please do not send credentials or sensitive documents through the enquiry form.

WORKING TOGETHER

From suitability assessment to a supported application

Understand the requirements and data

We clarify the use case, users, existing infrastructure and requirements for availability and access rights.

Test on a limited scale

A suitable solution is evaluated using selected data and workflows. Its limitations and any necessary adjustments are identified.

Plan setup and migration

We agree installation, permissions and any data migration. Your team or a local provider carries out hardware work on site.

Hand over operation

We discuss usage, documentation and responsibilities. Agreed support tasks are clearly distinguished from those handled by your team.

RELEVANT EXPERIENCE

Set up myself. Used in daily work.

My own Linux and Docker environment provides practical experience with installation, configuration and maintenance. We assess business requirements separately, particularly availability, access rights and responsibilities.

My own document management

Paperless-ngx with Linux and Docker

I run Paperless-ngx myself and work with document migration, imports, tags and permissions. This connects the initial setup with the questions that arise during everyday use.

My own infrastructure

Several applications on a NAS

On my UGREEN network storage, I run applications including Immich, AdGuard and Home Assistant. This personal small-office/home-office experience is a technical background, not an enterprise client reference.

QUESTIONS & ANSWERS

Questions about open source and self-hosting

Is self-hosting always better than a cloud service?

No. Requirements, available support and total costs determine the right choice. A managed service may be more suitable.

What responsibilities remain when we run the system ourselves?

Even without licence fees, updates, permissions, monitoring and backups need to be organised. Before setup, we agree who handles these tasks and what happens when something goes wrong. Installation alone does not replace ongoing support.

Can we use an existing NAS or server?

We assess processing capacity, storage, supported software and operating requirements. An existing NAS may suit some tasks and be inadequate for others. My personal small-office experience is not a blanket recommendation for business use.

How are backups and recovery taken into account?

We first establish which data needs protection and how much downtime or data loss your business can tolerate. This informs the backup approach, responsibilities and planned recovery tests. An existing backup is not assumed to work without verification.

How does setup work if you work entirely remotely?

Analysis and configuration require agreed, suitable remote access and an available contact person. Your team or a local provider connects equipment, changes drives and handles network cabling on site. We clarify these tasks and prerequisites before the appointment.

NEXT STEP

Which application would you like to host yourself?

Describe its purpose, your existing environment and who will use the system. We will assess suitability and ongoing effort before setup.

Your enquiry goes directly to me, Stefan Pilz. We agree the scope and costs before you commission any work.

What happens next

  1. Clarify the situation

    I read your enquiry and get back to you. Together, we clarify your goals, constraints and open questions.

  2. Choose a practical starting point

    Depending on the project, we start with a specific implementation or an analysis agreed in advance.

  3. Agree on scope and a proposal

    You know which services and deliverables are included. We agree on scope, effort and costs before you commission the work.

Enquire about self-hosting

* Required fields. A short description is enough.

I will reply to this address.

Which application would you like to run? Mention the functions you need, existing servers or hosting and who should look after the system afterwards.

This helps me get an initial impression.

Your information is used to process your enquiry. See the privacy policy for details. Please do not send login credentials or sensitive documents.

Sending an enquiry does not place an order.