For freelancers

The development platform for freelancers and solo developers

As a freelancer you are the developer, the project manager and the operations team. The Application Platform takes over setup, deployment and server operations so your hours go into billable work.

Every engagement starts with the project setup already done
Client projects stay separate, each with its own credentials
MCP server, ap CLI and VS Code plugin for AI coding agents

Start for free. No credit card required.

Several client projects side by side, cleanly separated.

In short

Working alone means there is no platform team behind you. That is the gap this fills.

Setup disappears. Repository, pipeline, server connection, domain and SSL are created with the project.
Several clients without the mess. Projects, roles and credentials stay separate per client.

Freelance work with and without a platform

This lines up the tasks that sit between the actual engagements when you work on your own.

Task	With the Application Platform	Without a platform
Project setup	Fully covered: Repository, structure, CI/CD pipeline, server connection, domain and SSL from the wizard	Not offered: Unbillable hours at the start of every engagement
Several clients in parallel	Fully covered: Projects and organisations separate clients, each with their own roles and access rights	Not offered: One machine, many local setups, credentials in several places
Servers and operations	Fully covered: Your own server over SSH or a managed one, with Docker, reverse proxy, SSL, firewall and backups	Partly covered: Servers maintained on the side, often only once something breaks
Deployment	Fully covered: Every merge runs through the same GitLab CI pipeline for test, build and release	Partly covered: Manual steps you have to relearn after three months away
Switching machines	Fully covered: Remote workspaces with VS Code, JetBrains, RDP or VNC, including macOS for iOS builds	Not offered: Everything depends on one laptop, and an outage stops all work
Mobile releases	Fully covered: Flutter, Expo and native projects into the App Store, Play Store and Microsoft Store	Not offered: Signing, certificates and store forms done by hand
Using AI coding agents	Fully covered: MCP server, ap CLI and VS Code plugin connect Cursor, Claude Code or Codex to the project	Partly covered: Agents work without clear conventions or a pipeline to check them
Production errors	Fully covered: Error tracking with Sentry is configured, with stack trace, release and context	Not offered: The client reports the bug, usually at the weekend
Handover at the end	Fully covered: Repository, pipeline configuration and server setup are readable and transferable	Not offered: Knowledge stays with you, which means questions months later
How you come across	Fully covered: Audit log, roles, GitOps and EU operation are concrete points for a proposal	Partly covered: Operations and privacy questions get answered from scratch per enquiry

Green means covered, amber partly, grey missing. The right-hand column is not a competitor but the usual state of things without an end-to-end platform.

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

What solo developers get

Six things that matter when nobody else cleans up behind you.

Billable hours back

Setup, pipeline and server groundwork are done before you start, so the saved hours go into work you can actually invoice.

Clients kept apart

Every project has its own credentials, roles and secrets. No client sees another one’s data, and you keep track of what belongs where.

Operations off your mind

Docker, databases, reverse proxy, SSL, firewall and backups are set up by the platform, on your server or a managed one.

AI agents with context

Environments and deployments live in Git history, so you can promise a client a system somebody else can pick up.

Work locally or in the cloud?

Entirely your call—we give you the ideal setup for both paths.

Local Platform App

Git & repos
Flutter SDK
Node.js
Docker

The setup app detects tools and starts everything with one click.

Cloud Remote workspace

Ubuntu VM
VS Code in browser
From anywhere

Ready-made dev environment—no local setup required.

Work locally or in a cloud workspace, depending on client and device.

What a new engagement looks like

Four steps from signing to the first deployment.

Create the project

Pick stack and platforms in the wizard. Repository, structure and CI/CD pipeline come with it, without copying old boilerplate.
Sort out the server

Use a managed server or attach the client’s server over SSH. The platform handles the baseline configuration.
Work wherever suits

Develop locally with the Platform App or in a cloud workspace. iOS builds run on a macOS machine from the platform.
Hand it over

At the end the client receives repository, pipeline and server setup. You adjust roles and access rights accordingly.

Frequently asked questions

Is a platform worth it when I work alone?

The comparison is not platform versus team, it is platform versus unpaid hours. Setup, pipeline and server groundwork come up in every engagement and rarely end up on an invoice. Getting started is free, so you can test the claim on one project.

How do I keep client projects apart?

Each project is its own unit with its own repository, environments and credentials. Organisations and roles decide who has access. Secrets are managed centrally rather than in local files, and the audit log shows which change happened when.

What if the client wants to continue without me?

Yes. You attach an existing server over SSH and the platform configures Docker, databases, reverse proxy, SSL, firewall and backups on it. Alternatively you take a managed server. A server dictated by the client works the same way.

Try it on your next engagement