There is no price on this page. Here is why.

What the maintainer team does sell

When an organization wants hands-on help, the maintainer team sells Professional Services: named engagements with named deliverables and named exit conditions. The catalog is at /services. Nine services, no prices on the page, the same way.

The three numbers that shape a price

1. The scope of the engagement. A four-week pilot with one team, one use case, and one deployment target is one number. A six-month multi-team rollout with migration, training, and a named on-call rotation is a different number. The Discovery gate is the conversation that names the scope.
2. The tenure of the engagement. A four-week pilot is a one-time engagement. A twelve-month retainer that includes a named on-call engineer and quarterly reviews is a different number. The Professional Services page is the menu; the Discovery conversation is the order form.
3. The environment the engagement runs against. A single-region VPS deployment is one number. A multi-region, air-gapped, or on-premise deployment with custom compliance controls is a different number. The Architecture Review is the conversation that names the environment.

The four-step path to a quote

1. Contact form. Fill in /contact?intent=quote with the named scope, the named tenure, the named environment, and a real human’s email address. An acknowledgement within one business day, from a real human, with the next conversation scheduled.
2. Discovery call. A 45-minute call with the maintainer team. The team names the Discovery brief and confirms it can support the named shape. A signed Discovery brief naming the scope, the tenure, the environment, the success criteria, and the price.
3. Written quote. Attached to the Discovery brief, valid for 30 days. Names the deliverables, the milestones, the exit conditions, and the price. The quote is the contract the engagement runs against.
4. Run the engagement. Sign, kick off, run. The maintainer team operates under the same Discovery brief, with the same named exit conditions, until the engagement ends. A working engagement and a written close-out report.

What the maintainer team will not do

• The team will not negotiate on the price for a scope it has not read. Every quote starts with a written Discovery brief.
• The team will not discount to close a quarter. The price is the price the engagement costs to do well; discounting it means doing it less well.
• The team will not bundle services the customer did not ask for. The catalog is at /services; the customer picks the ones it needs.

When OpenBean is the wrong fit

• A hosted or cloud version of OpenBean — there is none, and there will not be one. Self-hosting is the design, not a deployment option.
• 24/7 phone support on a four-hour SLA — the maintainer team is small. A four-hour-SLA support contract is not on offer today.
• A SOC 2 / HIPAA / ISO 27001 attestation from OpenBean the project — the compliance posture of your deployment is your deployment’s posture, not the project’s.

If any of these is what your organization needs, OpenBean is the wrong fit today. The honest answer is to use a different product, not to pretend OpenBean is something it is not.