bitbaum Start a project
Contract engineering · senior days · Zürich

We ship systems, and keep them running.

bitbaum takes a product from idea to a running, monitored, backed-up production service — and hands over something a normal team can maintain afterwards.

The studio is at capacity. The rates below are current, and the waitlist is how you hear first when a slot opens.

How we work

Four commitments that hold whether the engagement is two weeks or two years.

One verify command per repository Lint, typecheck, test. CI runs exactly that command, so green on your machine means green on the branch.
Everything ships through a branch and a pipeline The deliberate step is the pipeline, not a person remembering to click something.
Self-hosted by default, on Hetzner and Caddy Postgres, systemd, hardware you can point at. No per-seat pricing, no vendor lock-in, no surprise invoice.
Handover is designed in from day one Standard stack, full data export, documentation written for the engineer who arrives afterwards.

Questions people actually ask

Are these the real prices?

Yes. They are published so you can decide whether to have the conversation at all, rather than sit through a discovery call to learn a number. Fixed-scope work is quoted as a fixed price in writing before anything starts; day-rate work is invoiced monthly. No work begins on a verbal estimate.

How long is the wait?

We do not know, and would rather say that than invent a date. The list is worked in the order it was joined, and the only email it produces is the one saying a slot has opened. Joining costs nothing and commits you to nothing.

What happens if you become unavailable?

Handover is in the contract from the start: a standard stack, one command that runs the whole check suite, CI any engineer can read, and complete data export. You are buying a system a normal team can pick up — not anyone's availability. Ask your last supplier for a full data export and time how long it takes.

How do we know AI-written code is any good?

You don't — and you wouldn't for hand-written code either. That is what tests and pipelines are for. Nothing reaches a hosted instance without the full suite passing, and we are accountable for the output regardless of what typed it.

We need someone on site, full time.

Then you need an employee, and we will say so rather than sell you days that will not fix it. We are happy to help write the role and sit in on the technical interviews instead.

Can you do it cheaper?

Not by lowering the rate — by reducing the scope. Tell us which part can wait, and we will quote the rest honestly.

Join the waitlist

One message, typed or spoken, is the whole request. It opens a private portal where replies, status and previews appear — no account needed. When a slot opens, the list is worked in the order it was joined.

A reply from a person The request lands in the same system the work is run from, with everything you wrote attached. The answer comes from someone who read it, not an autoresponder.
It goes to us, nowhere else Stored on our own server in Germany — the infrastructure that runs everything on this site. No CRM, no tracker, no analytics profile, no third party.
Leave whenever Write the same way asking to be removed, and the record is deleted. There is no account to close, because there was never one to open.

The waitlist needs JavaScript to reach the studio. Read the pilot course or browse every project in the meantime.