Package Ecosystem
MarketHub packages are reusable BizFirstGO artifacts — from full workflow processes to individual node libraries. Every type of BizFirstGO artifact can be packaged, published, and discovered.
What Is a Package?
A MarketHub package is a versioned, self-contained collection of BizFirstGO artifacts bundled for redistribution. A single package might contain a complete business process workflow, the Atlas Forms that accompany it, and the custom nodes that power it — all installed together with a single click.
Packages are created by the InstallHub export system, which bundles artifacts into a standardized manifest format. MarketHub is then the storefront where these packages are listed, discovered, and installed.
Package Types
| Type | Source System | What it Contains | Typical Use Case |
|---|---|---|---|
| Flow Studio Package | Flow Studio | Workflow process definitions, sub-workflows, node configurations | Pre-built automation processes ready to customize and run |
| Atlas Form Package | Atlas Forms | Form definitions, field libraries, validation rules, layout configurations | Domain-specific forms (HR intake, expense approval, customer onboarding) |
| App Studio Package | App Studio | Full application: UI layouts, widget configurations, navigation, action bindings | Standalone data-entry or reporting applications |
| Node Library Package | ExecutionNodes | Custom execution node implementations extending the node palette | Specialized integration nodes (CRM connectors, payment gateways, custom logic) |
| Mixed Package | Multiple | Combination of the above — workflow + forms + custom nodes in one | Complete feature solutions deployed as a unit |
Package Anatomy
Every package shares a standard manifest structure, regardless of its type. This manifest is what InstallHub validates during export and what the public site renders on the package detail page.
{
"packageId": "uuid",
"name": "Expense Approval Workflow",
"version": "2.1.0",
"publisher": "publisher-slug",
"trustLevel": "Certified",
"category": "HR & Finance",
"artifacts": [
{ "type": "FlowProcess", "count": 3 },
{ "type": "AtlasForm", "count": 5 },
{ "type": "NodeLibrary", "count": 1 }
],
"dependencies": [
{ "packageId": "uuid-other", "version": ">=1.0.0" }
],
"pricing": "Free",
"installCount": 1842,
"averageRating": 4.7
}Package Pricing
Packages can be free or paid. Pricing is configured by the publisher when listing, subject to marketplace monetization being enabled on the platform instance.
| Pricing Model | How It Works | Revenue Split |
|---|---|---|
| Free | No charge — install limit may apply per tenant | No revenue |
| One-time Purchase | Tenant pays once, installs unlimited times within tenant | Publisher receives 70%, marketplace fee 30% |
| Subscription | Monthly or annual — access continues while subscription is active | Publisher receives 70%, marketplace fee 30% |
The paid package capability requires marketplace monetization to be enabled by the platform operator. On community or self-hosted instances, all packages are free.
Package Versioning
All packages follow semantic versioning (MAJOR.MINOR.PATCH). Users can install any version of a package, pin to a specific version, or always track the latest. When a publisher releases a new version, existing installs are not automatically upgraded — tenants control their upgrade cadence.
| Version Signal | Meaning | User Action Required |
|---|---|---|
| PATCH bump (2.1.0 → 2.1.1) | Bug fix, no API change | Optional — safe to upgrade |
| MINOR bump (2.1.0 → 2.2.0) | New features, backward compatible | Recommended — no breaking changes |
| MAJOR bump (2.1.0 → 3.0.0) | Breaking changes — incompatible updates | Review changelog before upgrading |
Package Dependencies
Packages can declare dependencies on other marketplace packages. When a user installs a package that has dependencies, InstallHub resolves the dependency graph and installs required packages automatically — if they are already installed and version-compatible, they are reused.
The InstallHub import pipeline validates the dependency graph for circular references before installation begins. Packages with circular dependencies are rejected during export.