Skip to content
Ninety days, eight deliverablesSee how
Nightshift

The Foundation

The environment every engagement runs on

Ingestion, storage, runtime and platform, provisioned as code into your own cloud account and identical in structure across customers.

What is in it

Four layers

  1. Layer 1

    Ingestion

    Connectors from your systems, plus a pipeline for the documents your records do not cover.

  2. Layer 2

    Storage

    A warehouse in raw, staging and mart layers, object storage, and a vector store for search.

  3. Layer 3

    Runtime

    Radiance, the service behind Claude Connect, scheduling and workflow execution.

  4. Layer 4

    Platform

    Identity, network, secrets, logging, monitoring, and the one outbound path out.

Why it is standard

The same environment for everybody

A bespoke platform per customer is how delivery businesses stop scaling and start charging for the same work twice.

Identical in structure

The foundation is the same environment for every customer. What differs is which systems connect to it and how the data is modeled on top.

Provisioned as code

It is built from infrastructure code committed to a repository you can reach, not assembled by hand and then documented afterward.

Improvements reach everyone

Because the environment is standard, work done on one engagement can be carried to the rest rather than trapped in a bespoke build.

The same environment for every customer, built from code rather than assembled by hand.

A bespoke platform per customer is how a delivery business stops scaling and starts charging twice for the same work.

What connects to it

Your systems, read where they are

Up to five source systems within the engagement, confirmed readable in the first week rather than assumed.

OdooNetSuiteQuickBooksXeroSage IntacctAcumaticaEpicorSAP Business One
SalesforceHubSpotShopifyAmazon Seller CentralZendeskJiraServiceNowADP
PostgreSQLSQL ServerAmazon S3SharePointGoogle DriveSFTPEDI feedsOutlook

Where it runs

In your cloud account, on your billing

You hold ownership access to the environment throughout. The only component we host is a single API that your environment pushes to.

  • Your cloud account, your bill

    We build into an account in your own name. Infrastructure and AI usage go on your bill at cost.

  • Read-only unless you sign it off

    Writing back into a system needs your approval in writing first.

  • Outbound only

    Nothing reaches into your environment from outside. It pushes out to one API.

  • Access you can audit

    The standing access we hold is written down and reviewable whenever you like.

Start with the numbers you cannot see today

Half an hour works out which measures are worth baselining and whether your systems can be read.