Skip to content
Aurum AI LabsAurum AI Labs

Open by design.

No model lock-in. No provider logins. Your stack, your cloud, our connectors.

See the structure. Keep control.
  • Published structure

    Understand the parts and their connections

  • Configurable behaviour

    Adapt how the work runs

  • Your environment

    Choose where the work lives

Nothing locks you in

Four things that stay open

All four are true today, and all four survive a procurement review.

  • Open models

    Explore Open models

    Bring your own keys. If you supply your own provider credentials you pay licensing, not markup.

  • Open connectors

    Explore Open connectors

    Your stack stays exactly as it is. We pull data from the tools you already run. We do not replace CDPs, CRMs, analytics or automation platforms.

  • Open deployment

    Explore Open deployment

    On our side, or in your own cloud where you need it.

  • Open framework

    Explore Open framework

    We publish the architecture and the practices. Nothing about how this works is a black box.

the rule

Publish the grammar, never the sentences.

Published structure

Structure yes — a marketing agent runs a locked sequence with named roles and a multi-model cross-check.

Private implementation

Recipe no — never the step-by-step inside a specific module.

What is published

Every part, named

What each part does, and whose it is.

Select a part to follow its connections.

ours to build

The run

Every run has a state you can see, stop, or pick up again.

The interfaceThe run

Start, follow and approve a run

ConfigurationThe run

Read the configuration at the start

The runSkills

Run the steps

The runMemory

Keep the run on record
Read every part
The run
Every run has a state you can see, stop, or pick up again.
Skills
Every unit of work is code, or the model deciding — declared, never inferred.
The model
One gateway, and the model chosen per step. Provider-agnostic by construction.
Capabilities
Data capabilities read from what you already run; action capabilities write back into it.
Memory
The Brand Brain, a run history, the signals worth keeping, and learnings — one boundary per organisation.
Configuration
Skills, capabilities, workflows and prompts are versioned records, not hard-coded logic.
The interface
An interface, not the system. No behaviour lives in it — results render from a schema.
The environment
The boundary everything else runs inside — secrets, egress, where data sits, and the audit trail.

How it is configured

Configured, not hard-coded

Content records

Skills
Capabilities
Workflows
Prompts

Edit the behaviour

Content changes.
No code release.

Version history

Previous versionKept for reference
Updated versionChanges recorded

See what ran, and what changed.

How configuration works

Skills, capabilities, workflows and prompts are records in a content system, versioned like any other content. Changing how a workflow behaves is an edit, not a release — and every version is kept, so you can see what ran and when it changed.

The practices

What makes the output hold up

  • A fixed sequence

    A locked sequence, the same every run, ending in verification.

  • Specialist roles

    Named roles, each with one job.

  • Models cross-check

    More than one model, cross-checking every judgement.

  • You approve

    Your approval before anything acts.

  • Clear accuracy bounds

    Honest accuracy bounds, stated rather than hidden.

Deterministic by default. The model is used only where judgement is genuinely required — and never as the last word.

Where it runs

Where it runs, and what that means for your data

On our side
  • Assess it
  • Try one workflow
Either side — you choose
  • Keep a workflow running
  • Run all workflows in one place
In your cloud
  • Have workflows built around you
Your keysYour audit boundary

Assess it and Try it run on our side. Keep one running and Run all of it in one place run on our side or in your cloud — you choose. Have it built around you runs in your cloud, on your keys, inside your audit boundary.

The catalogue of what can be connected is public: the platforms we read, and where we write back.

How you buy

What we never publish

The list is short, and it is the same list in every contract.

Kept private

  • Code

    Any code.

  • Content libraries

    What is in the CMS — the skill library, the module methodologies, the prompt library.

  • Scoring logic

    Aurum Score™ correlation logic.

  • Connector code

    Connector implementations. The catalogue is public; the code is not.

  • Brand context

    Any client's brand context.

One rule, from this page to the contract

  • Public

    The grammar is public

    The architecture and the practices — published, and checkable.

  • Yours

    Your sentences are yours

    • Audience clusters
    • Voice
    • Prompt library
    • Brand Brain contents
  • Ours

    Our sentences are ours

    • Skills
    • Module recipes
    • Aurum Score™ logic
    • Connectors
Assess it — free

Marketing Workflows, Automated.

The method is built in. You close in on the target.

Stop prompting. Start marketing.

Automate your marketing workflows

Assess it — see where you stand, free.