Contact

Book a briefing

Tell us about your organisation and what you want to protect. We will reply to arrange a private session. In that session we walk through the technology, run a live demo on your use case, and agree the scope of a design partnership. Detailed technical documents are shared only after an NDA is signed.

This form sends only when its script has loaded. If the fields stay greyed out, please email hello@dcslabs.ai instead. Nothing is sent from this page until then.

Briefing request

We work with government bodies, critical-infrastructure operators and large enterprises. Tell us a little about your organisation and we will get back to you.

01 About you
02 Your organisation
Organisation type

Organisation size

03 Your briefing
Area of interest

Choose all that apply.

When would you like to start?

Your role in the decision

Indicative budget for this initiative Optional

US dollars. Optional.

We use these details only to handle your request. They are stored with Cloudflare, our hosting provider, and emailed to our team's Google Gmail inbox; we do not sell them or use them for advertising. Privacy notice

01 The agenda

Three parts, in forty-five minutes.

01 · 15 MIN

The receipt format

One real receipt, field by field: what is signed, how it chains, and how it is anchored. We verify it live, then tamper with it.

02 · 15 MIN

The hybrid suite

Why every receipt carries Ed25519 and ML-DSA-65, what a verifier refuses, and how receipts stay checkable as algorithms change.

03 · 15 MIN

Your estate

A first sketch of where your cryptography lives, what to migrate first, and what evidence your regulator or board will want.

02 Who it is for

We tailor the briefing to the room.

You areWe bringRelated
A ministry, regulator or defence buyerSovereign verification, offline checks, and how evidence survives decadesGovernment
A bank, insurer or payments firmReceipts for agents that move money, and the human gate in front of spendFinancial services
A grid, water or telecom operatorGateway-based migration around running assets, and receipted control actionsCritical infrastructure
A platform or engineering teamThe MCP shim, the vectors, and how to verify in CIDevelopers
A space or autonomous-systems programmeEvidence that survives long delays, broken links and changes in cryptographySpace and autonomous systems
03 How we prepare

What we need, and what we never ask for.

USEFUL TO KNOW

A few lines is enough

Which agents or systems you run, roughly how large the estate is, and which regulations or deadlines you answer to. Public information is fine.

NEVER SEND

No secrets, ever

We will not ask for keys, passwords, credentials, network diagrams with addresses, or customer data, before or during a briefing.

Everything we show is labelled with its status: in production, staging, in development or planned.

04 Questions

Before you write.

What should we read beforehand?

Nothing is required. If you have ten minutes, the platform overview gives the shape of what we will cover.

Can we see it working on our own systems?

We agree that in the briefing, after an NDA, and we say clearly what is in production and what is in development before anything touches your systems.

Can the briefing be held under NDA or on site?

Tell us in the form what your organisation needs, and we will say what we can do.

Prefer to look first?

Verify a receipt in your browser, then come with questions.

Open the verifier