Self-hostable by design
Bus modules run as CLIs, API providers, portals, and workers that can be deployed in a customer environment or operated as a managed service.
Business Development Kit
BusDK gives teams a modular control plane for AI products: deterministic CLI tooling, authenticated APIs, event-driven workers, portals, VM and container runtime surfaces, billing, usage capture, and auditable workspace datasets. Run it with us on Finnish cloud infrastructure, deploy it in your own environment, or use it under a contract that defines the data-processing boundary.
curl -fsSL https://install.busdk.com | bash
Platform
Bus modules run as CLIs, API providers, portals, and workers that can be deployed in a customer environment or operated as a managed service.
Managed deployments can target Finnish cloud infrastructure while keeping the same module and API contracts available for other environments.
The LLM provider exposes /v1/* model proxy routes with Bus
authentication, backend isolation, runtime wake-up, usage capture, and billing
checks.
Cloud-neutral VM and container APIs coordinate with event workers, SSH runners, and provider-specific integrations such as UpCloud.
Bus Events and bus work provide request/reply, replay, fan-out, and
worker delivery paths for agentic and service workflows.
Passwordless login, scoped JWTs, billing setup, Stripe integration, usage export, and operator commands support real product operation.
Portal modules, accounting UI, AI portal surfaces, terminal providers, and chat modules give browser-facing entry points around the same APIs.
Accounting, invoices, banking, reporting, validation, and filing remain available as structured business-data modules for AI products that need traceable operations.
Deployment and data control
Heusala can operate BusDK-based AI products on Finnish cloud infrastructure, with service and data-processing terms agreed directly with the customer.
Discuss managed deploymentTeams that need direct infrastructure control can host the Bus modules, API providers, workers, portals, databases, and secrets in their own systems.
Read deployment docsCommercial deployments can define where data is processed, who operates the service, how secrets are supplied, and which support or licensing terms apply.
Contact salesUse cases
Use bus agent, bus dev, bus run,
bus work, and Bus Events to connect human review, local automation,
model-backed tasks, and durable worker delivery.
Combine Bus API, auth, LLM proxying, VM/container providers, usage collection, billing entitlements, operator commands, and portal modules.
Read LLM provider docsKeep finance, invoices, banking, validation, reports, filing, and evidence flows available as structured datasets for humans and AI systems.
See accounting workflowPricing
Subscription plans cover hosted and managed BusDK services. Self-hosted deployments, dedicated Finnish cloud environments, source access, support, and data-processing terms are handled by contract.
25 EUR/user/month
100 EUR/user/month
Source package licenses
Source code packages use the source-available Functional Source License (FSL). Alternative commercial licensing is available by contract. After two years, each release converts to Apache 2.0 or MIT. Source access, self-hosted deployments, dedicated environments, and alternative commercial terms are quoted by agreement.
Current source-package estimates are generated from the pricing data model. Final quotes depend on contract scope, deployment model, support, and licensing terms.
bus, docs, and busdk.com are open source and
excluded from source package license pricing.
Base estimates are allocated by module commit share. Dependency-inclusive estimates include the selected module and its transitive BusDK dependencies.
BusDK favors deterministic command surfaces, explicit API boundaries, scoped tokens, evented workers, and open workspace data so AI automation remains inspectable.
Deployment is a contract boundary as much as a technical choice: customers can use a managed Finnish cloud service, a dedicated environment, or their own infrastructure.
Learn the architecture in docs.busdk.com/architecture and the core dispatcher in github.com/busdk/bus.
Start with the documentation, then evaluate the CLI, API, runtime, billing, portal, and business-data modules against the deployment model your product needs.