Delivery Hub Overview
Open Source

Delivery Hub Install Strategy

Choose the right approach for your Salesforce org.

What is Delivery Hub?

Delivery Hub is an open-source, Salesforce-native project delivery platform. It tracks work from request to completion with built-in process steps, field change history, dashboards, and notifications. It can be installed as a managed package (under the nimba__ namespace) or deployed as unmanaged metadata from the public GitHub repo. This page helps you decide which approach is right for your organization.

Managed Package

Install in minutes. Auto-upgrades. nimba__ namespace isolates DH from your metadata.

Unmanaged Fork

Full control over every line. No namespace. You own the maintenance.

Hybrid

Managed core + unmanaged extensions. Auto-upgrades where it matters, custom where you need it.

Three Approaches

Click each option to see full pros, cons, and implementation details.

Option A: Managed Package

Install Delivery Hub as a managed package from Salesforce Setup. The nimba__ namespace keeps DH completely isolated from your custom metadata. You get automatic upgrades when new versions ship, zero maintenance overhead, and clean separation between DH and your org's customizations.

Recommended
Best For

Orgs that want to use DH out of the box, don't need deep customization of DH internals, and value low maintenance.

Pros

One-click install from Salesforce Setup
Automatic upgrades -- new features, bug fixes, and enhancements land automatically
nimba__ namespace keeps DH isolated from your custom metadata
Clean separation -- DH code never collides with your existing objects or classes
AppExchange-ready -- familiar installation model

Cons

Cannot modify DH internals -- objects, Apex classes, and components are locked by namespace
Namespace prefix (nimba__) on all DH references in your custom code
Dependent on package publisher for updates (though existing install keeps working indefinitely)
Effort
15 minutes
Risk Level
Low
Future-Proof
High

Side-by-Side Comparison

Every dimension that matters for this decision.

A: ManagedRECB: UnmanagedC: Hybrid
Auto-upgradesYesNoYes (core)
CustomizationExtensions onlyEverythingExtensions + core untouched
Migration effort15 min install2-4 hours15 min + extensions
Future featuresAutomaticManual mergeAutomatic
IndependencePartialFullHigh
MaintenanceLowHighLow-Medium
Namespace prefixYesNoOn DH refs only

Which Should I Choose?

Answer a few questions to find the right fit.

1

Do you need to modify DH core objects, Apex classes, or LWC components?

YesOption B (Unmanaged)
No? Continue...
2

Do you need org-specific workflows, automations, or custom UIs on top of DH?

YesOption C (Hybrid)
No? Continue...
3

You just want to use DH as-is with minimal setup?

Option A (Managed Package)-- Recommended for most orgs

Getting Started

Ready to install Delivery Hub? Start with the managed package for the fastest path to value. Fork the repo if you need full control. Either way, it's free and open source.

Frequently Asked Questions

Common questions about Delivery Hub installation and maintenance.

Cloud Nimbus LLC — Delivery Hub is free and open source