Bus Services Pricing

Choose how your team runs Services.

Bus Services is available as a binary subscription, an FSL source-available subscription that converts to MIT or Apache 2.0 two years after release, or a one-time MIT source release. The binary subscription includes a two-week free trial so teams can validate service stacks before the monthly plan starts.

Compare options Start with Services Contact sales@hg.fi

Purchase options

Binary Subscription

Use this when your team wants the supported Bus Services binary for stack validation, planning, startup, status, and shutdown workflows. Includes a trial period through Stripe. Source repository access is not included.

FSL Source Subscription

Choose this when your team needs source-available access under FSL terms, Git repository access, setup instructions, and issue-tracker support while the subscription is active. Source converts to MIT or Apache 2.0 two years after release.

MIT Source Release

Use this when you need a permissive MIT-licensed source release instead of a recurring source subscription.

What each option includes

Option	Purchase path	Purpose
Free trial	Stripe checkout	Evaluate the binary workflow before the subscription starts.
Binary Subscription	Stripe checkout	Run the Bus Services binary for local stacks, Docker images, and repeatable operations. Source repository access is not included.
FSL Source Subscription	Stripe checkout	Use source-available Bus Services modules with Git repository access and issue-tracker support while active. Source converts to MIT or Apache 2.0 two years after release.
MIT Source Release	Stripe checkout	Receive a permissive MIT-licensed source release for the Services modules.

Included modules

`bus-services`

The user-facing Services CLI and profile surface for validating, planning, starting, listing, and stopping service stacks.

`bus-api-provider-services`

The API-hosted Services lifecycle surface for provider-backed service creation, inspection, and control.

`bus-integration-services`

The runtime integration layer for local supervision, stack state, status, and process lifecycle behavior.

Start before buying

Prove the operational workflow first: define a stack, run bus services up, inspect with bus services list, and stop with bus services down. If the stack becomes part of a team workflow, continue with the binary subscription or choose source access when your team needs to inspect and adapt the implementation.