For SMBs and mid-sized companies

The development platform for mid-sized companies with in-house IT

Mid-sized companies often build software with a small team on a setup that grew over years. The Application Platform standardises setup and operations without abandoning existing servers or compliance rules.

Your own servers over SSH, or managed servers inside the EU
Audit log, roles and access rights instead of grown permissions
Operational knowledge in the repository, not in individual heads

Start for free. No credit card required.

The audit log shows who changed what and when.

In short

The bottleneck in a mid-sized company is rarely development itself, it is the surrounding work nobody wrote down.

A standardised setup. Repository, pipeline, server, domain and SSL follow the same rules everywhere.
Your infrastructure stays yours. Attach existing servers over SSH or take managed servers inside the EU.

A grown setup next to a standardised platform

This lines up the work a small IT or development team deals with, and that has been solved differently over the years.

Task	With the Application Platform	Without a platform
Project setup	Fully covered: Repository, structure, CI/CD pipeline, server connection, domain and SSL follow one set of rules	Not offered: Every project carries the handwriting of whoever set it up
Operational knowledge	Fully covered: Environments and deployments live as readable configuration in Git history	Not offered: Knowledge sits in scripts, wiki pages of uncertain age and individual colleagues
Using your own servers	Fully covered: Attach existing servers over SSH or use managed servers	Partly covered: Possible, but every machine is maintained on its own
Server baseline	Fully covered: Docker, databases, reverse proxy, SSL, firewall and backups are configured automatically	Partly covered: Manual setup, documented afterwards at best
Roles and access rights	Fully covered: Organisations, roles and access rights govern access per project and environment	Partly covered: Permissions grew historically and are rarely cleaned up
Evidence for audits	Fully covered: An audit log of relevant changes plus GitOps history for environments and deployments	Not offered: Evidence gets assembled shortly before the audit date
Where processing happens	Fully covered: Operated in the EU, GDPR compliant, data processing agreement available	Partly covered: Individual services sit outside the EU and have to be assessed one by one
Onboarding and cover	Fully covered: Remote workspaces with VS Code, JetBrains, RDP or VNC start ready to use	Not offered: New colleagues need days before an environment runs
Production errors	Fully covered: Error tracking with Sentry, including stack trace, release and context	Partly covered: Errors arrive through support and get classified by hand
Provider dependency	Fully covered: Repositories, pipeline configuration and servers belong to the company, with full code ownership	Partly covered: Individual tools and contractors are replaceable only with effort

Green means covered, amber partly, grey missing. The right-hand column is not a competitor but the usual state of a setup that grew over years.

As of 10 August 2026. This comparison describes typical workflows and can differ from project to project.

What an SMB with in-house IT gets

Six points about operational safety and being able to prove things.

Your servers stay your servers

Existing machines are attached over SSH and configured with Docker, reverse proxy, SSL, firewall and backups. Managed servers are the alternative.

Operated in the EU

Processing and hosting happen in Europe, GDPR compliant and with a data processing agreement, so responsibilities are contractually settled.

A history that holds up

The audit log records the relevant changes. With the Git history of your environments, that produces a trail you can show an auditor.

Roles instead of grown access

Every project uses the same GitLab CI stages for test, build and release, which makes approvals and releases a repeatable procedure.

Anna Weber
Organization, members & billing

Administrator
Max Schneider
Code, Git & deployments

Developer
Tom Richter
QA on dev & staging

Tester
Paul Klein
Customer app & feedback

Customer

Roles and permissions instead of knowledge tied to individuals.

Replacing a grown setup step by step

One pilot project first, then controlled rollout.

Agree the ground rules

Decide which servers may be used, where which data is processed and which roles should exist.
Run a pilot

Pick a project with a clear scope, create it in the wizard and attach an existing server over SSH.
Write down the standard

Adjust the pipeline configuration in the repository to your internal requirements. The result becomes the template for further projects.
Move the estate across

Existing applications follow gradually, sensibly bundled with updates or relaunches that are due anyway.

Frequently asked questions

Do we have to replace our existing infrastructure?

No. You attach existing servers over SSH and the platform configures Docker, databases, reverse proxy, SSL, firewall and backups on them. Managed servers are the alternative. Kubernetes and monitoring are announced but not yet available.

How does this help with an audit or certification?

The platform supplies the technical traceability auditors ask for: an audit log of relevant changes, documented roles, and environments and deployments as configuration in Git history. The assessment itself remains a matter for your management system.

What happens when the colleague who knows everything is unavailable?

The model is a platform base price plus add-ons for users, workspaces and CI minutes; current numbers are on the pricing page. Server costs arise wherever you host. Getting started is free, so a pilot can begin without a procurement process.

Begin with a pilot project