Use Cases — InstallHub Overview

Cross-Environment Promotion

Dev → Staging → Production Pipeline

Teams build and test workflows in a development tenant, then promote them to staging and production using InstallHub packages. This eliminates the risk of manual recreation errors and ensures every environment runs the same tested artifact versions.

Scenario: The HR team builds an employee onboarding workflow in dev. QA tests it. On sign-off, a platform engineer exports it as onboarding-v2.1.0.zip and imports it to staging with conflictStrategy: Replace to overwrite the previous staging version. After staging sign-off, the same package is imported to production.

Key benefits:

Every environment runs the exact same artifact, checksum-verified
Rollback is possible by re-importing the previous package version
Audit log records who imported what and when in each environment

Team Sharing

Sharing Components Across Teams

A platform team builds reusable workflow templates, form libraries, and rule sets that other teams can import into their own tenants. InstallHub packages provide a clean handoff mechanism without requiring access to the source tenant.

Scenario: The Finance team builds a standard expense approval workflow that other departments want to reuse. They export it as a workflow-package, post the ZIP to an internal file share, and each department imports it into their own tenant. The import pipeline remaps IDs automatically so there are no collisions.

Seeding New Tenant Environments

When provisioning a new customer tenant, a "starter pack" of baseline workflows, forms, and configurations can be imported automatically as part of the tenant setup process. This ensures every new tenant starts with the same foundation.

Scenario: A BizFirstGO SaaS operator maintains a starter-pack-v1.0.0.zip that includes the default dashboard app, user management forms, and core notification workflows. Every new tenant receives this package on sign-up.

Marketplace Distribution

Publishing to the Community (Phase 3)

Once Phase 3 (Marketplace) is live, teams can publish packages to the public InstallHub marketplace (PublicHub) for the global BizFirstGO community to discover, preview, and install. This enables a thriving ecosystem of reusable automation components.

Scenario: A consulting firm builds a best-practice HR onboarding suite for BizFirstGO. They publish it to the marketplace with Certified status (after human review). Other companies find it via marketplace search and install it with one click, triggering the Phase 2 import pipeline.

Industry Vertical Templates

BizFirstGO's Official packages provide industry-specific workflow templates — healthcare intake forms, financial KYC workflows, logistics tracking processes — that organizations can install and customize in minutes rather than building from scratch.

Disaster Recovery and Backup

Point-in-Time Artifact Snapshots

Periodically exporting key workflows and forms creates point-in-time snapshots that can be stored in version control or blob storage. If an artifact is accidentally deleted or corrupted, it can be restored by re-importing the snapshot.

Scenario: A nightly CI/CD job calls the export API to snapshot all critical workflow definitions to a Git repository. The commit history provides a full version history of every workflow. Rollback to any previous version requires only re-importing the corresponding ZIP.

Multi-Tenant SaaS Deployment

Deploying Updates to All Customer Tenants

SaaS operators using BizFirstGO to power their product can use InstallHub to deploy workflow and form updates to all customer tenants in a controlled, audited fashion — with per-tenant conflict resolution settings.

Scenario: A payroll SaaS product built on BizFirstGO releases a new payroll calculation workflow. The operator imports payroll-calc-v3.0.0.zip into each customer tenant using an automated script that calls the import API with conflictStrategy: Replace and dryRun: true first to preview impacts.

← The Package Concept Next: Architecture →