Done for you
Have us do the parts you would rather not.
The software is free. The afternoons are what we sell. Run BenchPress yourself and it costs nothing but a server — these are the four engagements for when you would rather hand a piece of it over.
You may not need us
The install is documented step by step, and self-hosting is free forever with no account and no ceiling on labs. If you have a spare Linux box, a Frappe v16 bench and an afternoon, do it yourself — the guide exists so that you can. Pay us when the afternoon is worth more than the money, or when you want the host to be somebody else's problem.
The four engagements
-
Managed hosting
We run the host, the WireGuard plane and the upgrades. Your team gets a console, a credit balance and a ledger that shows every line.
- A host we run, patch and watch
- Per-device WireGuard keys, revocable in a click
- Nightly database dumps, and the restore path tested
- Upgrades, including the lab images
Not production hosting. BenchPress runs development and demo environments; a live client site does not belong on it.
What we need from you. Your app list and the Frappe versions your team works on.
-
Setup on your server
One engagement, on your machine, ending in a deploy you watched succeed. The same six steps the guide describes, done by someone who has done them before.
- The preconditions checked on the host before anything is installed
- Both apps installed, the setup script run under --strict
- WireGuard configured and your first device enrolled
- Your lab templates seeded, and a first deploy proven green
- The twelve diagnostics run in front of you, and the keys handed over
Not buying, sizing or hardening the server. That stays yours.
What we need from you. Shell access to a host that meets the prerequisites, and a domain you control for the base domain.
-
Custom Frappe apps
The app your process actually needs, built against a BenchPress lab so every review runs on a real site with your app set and your version.
- A lab template pinned to the versions you run
- The app, its tests and its documentation
- A review at the end of each sprint, on a live environment you can open
Not hosting the result. Deploy it wherever your production lives.
What we need from you. Whoever owns the process, available for one review per sprint.
-
Team training
So the next new joiner onboards themselves, and nobody senior is the environment help desk any more.
- Labs and templates: defining a stack once and handing it out
- The deploy pipeline, and reading the step that failed
- The VPN, devices and the browser VS Code session
- What to do when a build dies, and where the logs are
Not a Frappe development course. This is the environment, not the framework.
What we need from you. The team, half a day, and one host they can all reach.
How an engagement starts
-
A 20-minute call
Team size, the server you have, and what breaks today. No deck, and no obligation to buy anything.
-
A scope in writing
What is included, what is not, and what we need from you — the three things every engagement above already names. If we think you should do it yourself, we say so.
-
The work, then a handover
Fixed scope for a setup, by sprint for app work, monthly for hosting. Every engagement ends with the credentials, the documentation and a working deploy in your hands.
Tell us what breaks today.
Requests are read by a person, not a queue. Say the team size, the server you have and what is costing you afternoons, and we will say plainly whether you need us at all.