Home / About

No mission statement. Just positions.

You're considering software that will sit in the path of every action your agents take. That's a reasonable moment to want to know what we think and where we won't bend — so this page is a list of positions, each one shown beside what it costs us to keep holding it.

Where this came from

We built the agents first.

Which is how we found the gap. You don't notice it from the outside.

Digital Spectre started as a team shipping agentic systems for other people's businesses. Workflow automation, retrieval, orchestration, integration — the work went well and the agents did what they were built to do.

The uncomfortable part came later, in the handover conversations. Clients would ask a version of the same question — so how do we know what it's doing now? — and the honest answer was that they'd see the output and very little else.

We were handing over software with standing production access and no supervision, and calling it delivery.

Nothing on the market treated an agent the way an organisation treats a person with the same access: baselined, scored, held when something looked wrong, and on the record afterwards. So we built that, and it turned out to be the more important half of the work.

We still build agents. We just no longer ship one that nobody can watch.


What we hold

Seven positions, and their price.

A belief with nothing attached to it is marketing. Each of these costs us something real — revenue, speed, or an easier product to build.

If we ever quietly drop one, this page is where you'll be able to tell.

The positionWhat it costs us
01

Observe before you enforce

Nothing blocks on day one. An agent runs traced and unrestricted until you've seen enough of its behaviour to write rules that reflect it.

The price

A slower path to the paid tier. We're deliberately telling people to spend a quarter not paying us, and some of them never move past it.

02

It runs in your cloud, not ours

The enforcement layer deploys into your own account. Your traces stream to your own bucket. We hold no production credentials at any point.

The price

Harder operations, slower debugging, and no data moat. The usual argument for a single-tenant SaaS is that it's easier for the vendor. It is.

03

Your data trains nothing

Not our models, not a third party's, not aggregated, not anonymised. It isn't a setting and it isn't negotiable at any price.

The price

We give up the flywheel every AI company is told it needs. Our product improves because we build it, not because you use it.

04

Console seats are unlimited

On every tier, including free. Security, operations and compliance reading one record is the entire argument — charging per reader would contradict it.

The price

We hand back the easiest pricing lever in software. Per-seat expansion is how most platforms grow revenue without shipping anything.

05

Leaving should be a decision, not a project

Ninety days of access after termination, a full export, and a hash chain anyone can verify without us. Agents keep running even when enforcement stops.

The price

We remove our own switching costs. Every renewal has to be won on whether the product is still worth it.

06

We turn down work that doesn't fit

Low volume with catastrophic failure, outcomes nobody can define, teams who haven't been told. We say so in the first fortnight rather than the fourth month.

The price

Signed deals we don't take. It's the most expensive position here and the one we're most often asked to bend.

07

It's a control, not a guarantee

Spectre reduces the chance of a bad agent action landing. It does not promise to catch every one, and we won't let a sales conversation imply otherwise.

The price

A weaker pitch than competitors willing to say "never". We'd rather lose that deal than be quoted back this sentence after an incident.


How we're built

Small, and intending to stay useful.

The fair question about a company in our critical path is whether it'll still be here. Here's what we can tell you about that.

Engineers, mostlyThe people who'd run your engagement are the people who built the platform. There is no separate solutions team to hand you to.
We were the agency firstWhich is why the platform is opinionated. Every guardrail exists because a client asked a question we couldn't answer.
Revenue before scaleWe'd rather have fewer customers who renew than a chart that goes up for four quarters and then doesn't.
Your exit is prepaidIf we did disappear, your agents keep running and your trail stays verifiable. That shouldn't be reassuring, but it's true.

Roadmap discipline

Things we keep being asked for and keep not building.

Each of these would sell. Each would also make the product worse at the thing it's for.

A model of our ownEvery conversation about building one is a conversation about not improving supervision. Bring whichever model you like.
Employee monitoringWe're asked roughly monthly. Spectre watches software acting on your behalf, and pointing it at people would be a different company.
An agent marketplaceWe'd be selling you agents and supervising them. You should not buy the referee from the team.
A risk score you can show a regulatorOur number is useful internally. Presenting it as an external compliance grade would be inventing an authority we don't have.
Get started

Disagree with one of these?

Tell us which. The positions on this page have been argued into shape by customers, and the ones that survived did so because someone pushed hard on them first.