What Cloud Nimbus and Delivery Hub Shipped Since I Signed the Lease

I signed my own apartment lease using my own software on April 8. The day after that I shipped a tenant screening platform in 48 hours. Then I went quiet on the blog for two weeks.

I was not quiet on the keyboard.

Here is what Cloud Nimbus and Delivery Hub shipped between April 9 and today, in the order they matter.

1. PR #700 — the integration framework

This is the headline. Delivery Hub now has a generic integration dispatcher: one Custom Metadata Type, zero per-system code, four live providers, a webhook receiver, and an admin LWC to wire them up. Before #700, every new outbound system meant new Apex. After #700, it's a metadata row.

This is the kind of refactor that doesn't move a single user-visible pixel and quietly cuts the cost of every future integration to a fraction of what it was. It also unblocks a thing I have been wanting to do for a year: let an admin (or a Claude, or an automation) plug a new system into Delivery Hub without writing code. Slack notifications. QuickBooks line items. A custom HTTP webhook to a partner. All four are live in the framework today. The fifth is a config row away.

PRs #701 through #710 were the cleanup pass — PMD compliance, namespace fixes, exception class extraction, the kind of polish you only catch once the framework is real. Worth listing: that is eleven merged PRs in a single architectural arc, which is the cadence I wanted to be writing about a year ago and was not.

2. Delivery Hub v0.99 shipped

Tagged release. Three real user-facing wins:

• Invoice client picker — the invoice flow now lets you pick the client at composition time instead of inferring it from project context. Sounds boring. Was the #1 friction point for the production users I spent the last quarter watching.
• WorkLog sync pending queue — when a WorkLog can't sync immediately (org busy, callout limit, transient failure), it now queues and retries instead of silently failing. Nobody loses an hour entry to a bad network anymore.
• Blank WorkItem rejection — you cannot create a WorkItem with no title. I cannot believe this was ever possible. It is no longer possible.

v1.0 is two cuts away. The next two cuts are the audit-preview modal (already in the bundle, just not wired on DH) and batch-mode commit. After that, the version number stops being a beta signal.

3. The Gantt grew up

Two weeks ago you could drag a bar to reschedule it. That was already the headline feature. Since then:

• Right-click context menu with create-dependency / delete-dependency on every bar.
• Dense sortOrder renumbering done server-side so reorders stay 1..N forever instead of drifting into floating-point chaos.
• Show/Hide Header toggle in the title bar so the chart can claim the full viewport when you need it to.
• Standalone Aura app that bypasses Salesforce FlexiPage chrome entirely — the same Gantt rendering inside a /lightning/n/ URL with zero breadcrumbs, zero sidebar, just the planning surface.
• Cross-org dependency rendering so a WorkItem on one Salesforce org can show its parents and children from another.

The Gantt now does most of what teams pay Bryntum or DHTMLX five-figure annual licenses for, except it lives directly on top of the Salesforce records that are already your source of truth. No exporting. No two-system drift. No "let me check Asana real quick."

4. Cross-org file sync, the right way

The old file-sync code inlined VersionData in the JSON payload. That works at small scale and detonates the moment somebody attaches a 10MB PDF. I rewrote it to post a metadata-only payload first, then pull the file bytes via an authenticated callback. Apex governor limits stay happy. Large files survive. The payload size is bounded regardless of attachment size. This is the kind of thing you have to ship once, in the boring way, before the customer who attaches a 200MB CAD file shows up.

5. The GVS refactor I had to revert

Honesty pass. PR #691 swapped four high-churn picklist fields to GlobalValueSet references. Phase 2 of a tidy little refactor. Salesforce blocks retrofitting GVS onto existing custom fields if any subscriber org has data in those fields. I did not know that until I tried it. PR #692 reverted #691 the same day.

The lesson is small but worth carrying: a managed package's freedom of motion is constrained by every customer who has already installed an earlier version. You cannot just refactor the schema cleanly the way you would on a single-org build. I learned the rule by hitting it. Better here than in production. The trigger-layer picklist allowlist enforcement (PR #693) accomplishes the same defensive goal with no schema change.

The state of the eight verticals

Cloud Nimbus runs eight vertical SaaS products on Delivery Hub. All eight are live. The split as of today:

1. Tenant Screening — live, taking Stripe payments
2. Lender Workflows (Mobilization Funding) — production, ~70 routes
3. Consultancy Delivery — production, eat-our-own-dogfood
4. Salesforce Development — production, the reference workflow
5. IT Helpdesks — live
6. HR/IT Onboarding — live
7. Change Management — live
8. Operations — live

The same Delivery Hub install runs all eight. That is the entire bet: build the platform once, white-label the verticals.

Install link, again

I am going to keep saying this until enough people click it.

If you run a Salesforce org and you wish your delivery work, your invoicing, your hour tracking, or your client onboarding lived in fewer tools — install Delivery Hub. It's free to try. The package drops directly into your org. The same e-signature flow that carried my own apartment lease is in there. The same Gantt that runs the Mobilization Funding production workflow is in there. The integration framework that just landed in PR #700 is in there.

If you want the engineering-blog version of how this gets built, the Four Claudes and a Gantt post is the closest thing to a process tour I have written.

Talk minus action equals zero. Two weeks ago I signed a lease on my phone in front of my real estate agent using software I built. Since then I have shipped eleven merged PRs on the integration framework, the v0.99 release, a Gantt with right-click dependencies and cross-org parents, a fixed file-sync that survives attachments, and one revert that taught me a Salesforce platform constraint I will never forget.

The cadence is the product.