DDC Assurance Lab is not an accredited laboratory.

Services

Choose the assurance outcome, not a repository name.

DDCAL organizes client work around the problem to be assured. Technical methods and tools remain visible under Technology.

Core assurance services

Start with the assurance question.

Independent assurance, incident reconstruction and runtime/action assurance are the primary service families. Demonstrations and named technologies are supporting capabilities, not competing service names.

Limited pilot candidate

Independent AI Assurance

Two independently produced determinations over one frozen evidence set, followed by controlled comparison and attestation.

Explore Independent Assurance →
Incident analysis

Incident Reconstruction

Reconstruct action lineage, evidence timing, retries, divergence and unresolved consequence without inventing certainty.

Explore Incident Reconstruction →
Runtime & execution

Runtime & Action Assurance

Assess authority, policy, evidence, prerequisites, state transitions, execution boundaries and downstream observations.

Explore Runtime & Action Assurance →
Free · Working demo

Try DDC

Submit a public GitHub repository URL, run bounded read-only analysis, and download a review PDF. No submitted-code execution.

Open Try DDC →
Open source · Local option

Try DDC on GitHub

Inspect the public analyzer and run it in your own GitHub Actions environment so target source stays on your runner.

View repository →
Open source · Compute

RadialD

Authority-safe concurrent work coalescence and lineage-aware shared-prefix execution for deterministic workloads.

Explore RadialD →
Technical assurance

Assurance services

Defined-scope systems, evidence, security, conformance and closure assessments with explicit limitations.

Explore assurance →
AI & agents

AI agent assurance

Assess delegated authority, tools, state transitions, verifier independence and execution boundaries.

Explore agent assurance →
Repository analysis

Repository security preflight

Understand the exact-commit static preflight, representative findings and limits of the public demonstration.

Explore repository analysis →
Software & transitions

Software conformance

Review requirements, predecessor state, execution, postconditions, evidence and acceptance boundaries.

Explore conformance →
Blockchain & smart contracts

Blockchain assurance

Read-only contract and on-chain assessment: source/bytecode, proxies, admin roles, invariants, bridges, oracles and transaction evidence. Scoped separately.

Explore blockchain assurance →
Custom scope

Request an assessment

Define a target and question for a private system, specialist review or evidence set that does not fit a fixed-scope service.

Start an inquiry →

Demonstration boundary: Try DDC is a reduced public preflight, not a controlled assurance report. Specialist pages describe assessment capabilities and are not additional live demo endpoints. RadialD is a compute tool, not an assurance verdict.

Fixed-scope assurance

Start small. Buy a defined review.

Three bounded services provide a low-friction path from a public repository review to a deeper pre-launch assessment. Prices are one-time and in Canadian dollars.

Entry review

DDC Snapshot

C$15 one-time

A bounded assurance snapshot for one public GitHub repository.

  • One public GitHub repository
  • Exact repository state resolved before review
  • Read-only/static preflight
  • Material assurance observations
  • Concise digital result and next steps

Typical input: a public GitHub repository URL and the primary question you want DDCAL to challenge.

Not included: private evidence handling, code execution, certification, accreditation, or a comprehensive security audit.

Buy DDC Snapshot

Pre-launch

Pre-Launch Assurance

C$249 one-time

A deeper bounded review for one eligible software or AI system before release or a material transition.

  • Architecture and authority-boundary review
  • Prioritized findings
  • Remediation guidance
  • One post-fix verification cycle
  • Digital assurance report

Typical input: a defined system, the release/version/commit under review, and the primary claim, invariant, failure condition, or concern you want challenged. Supporting architecture, requirements, configuration, test, or verification evidence can be brought into the agreed scope after intake.

Scope note: unusually large, private, confidential, or complex systems may require a separately agreed evidence-transfer or scope boundary before substantive work begins.

Buy Pre-Launch Assurance

Blockchain & smart-contract assurance

Smart-contract and blockchain work is available as a separately scoped technical assessment rather than being silently forced into one of the three software checkouts.

Static

Smart-contract source review

Public Solidity/EVM source, repository structure, access control, invariants, external-call risk and other bounded static findings. No signing or deployment authority.

On-chain

Deployed identity & authority

Read-only inspection of chain ID, contract address, bytecode/source correspondence, proxies, implementations, privileged roles, oracles, bridges and other material dependencies.

Full bounded

Contract + deployed-state assurance

Source, deployed identity, authority topology and bounded static/dynamic/adversarial analysis with independent verification and explicit release acceptance.

What do you enter at checkout?

Stripe checkout collects only the information needed to identify the purchase and begin bounded intake. It is not an evidence-upload form.

Target

Public URL or PRIVATE

Enter the public project/repository URL. For a non-public system, enter PRIVATE so DDCAL can confirm scope before any non-public material is transferred.

Question

What should be challenged?

State the primary review question, expected behaviour, invariant, authority boundary, failure condition, or concern. Customer text is treated as intake evidence; it cannot expand the purchased technical capability.

Email

Where the accepted result goes

After payment is independently verified, DDCAL sends the job acknowledgement to the email used at Stripe checkout. The accepted final report is delivered to that same checkout email unless a secure private-evidence delivery path is required.

What evidence can an assessment use?

Depending on the service and agreed scope, an assessment can use a URL, actual files, on-chain state, or a combination. The evidence does not have to be a Git repository.

URL / address

Public target or evidence locator

Examples include a public source repository, stable product or release page, live software URL, API or technical documentation, blockchain network + contract address, browser-extension listing, or another public target that identifies the system being assessed.

Files

Supporting evidence package

Examples include source or configuration files, bounded source archives, requirements and architecture documents, manifests or SBOMs, test output, logs or traces, screenshots, prompt or tool-policy files, deployment configuration, and representative non-sensitive test data.

Claim

Defined decision boundary

Provide the exact version, commit, deployed contract state, or block boundary and the claim you want challenged. DDCAL uses the agreed scope—not the volume of submitted material—to determine what the assessment is authorized to test.

What happens after payment?

1 · Verify

Stripe payment is independently checked

The checkout success page is never payment proof. DDCAL verifies the signed Stripe event and independently re-reads the Checkout Session before creating a fulfillment job.

2 · Assess

Work stays inside the purchased boundary

The verified service maps to a fixed DDC capability profile. Repository text, customer instructions, on-chain data, or payment itself cannot silently authorize broader execution.

3 · Deliver

Accepted report + integrity evidence

Public or low-sensitivity accepted reports can be delivered as a PDF with a detached SHA-256 file. Private/confidential reports use a controlled secure-delivery path when email attachment would violate the evidence boundary.

Before you pay

Scope

One bounded target

Each listed price applies to the stated fixed scope. If the submitted target cannot reasonably fit that scope, DDCAL contacts you before substantive work begins rather than silently widening the service.

Evidence

No secrets in checkout or email

Do not submit passwords, API keys, private-repository tokens, wallet seed phrases, private keys, proprietary datasets, personal information, executables, or confidential evidence through Stripe fields or ordinary email.

Status

Technical assurance, not accreditation

DDC Assurance Lab is not an accredited laboratory. These services do not constitute certification, legal advice, a financial audit, or a guarantee that a system is defect-free.

Need a different scope?

Start with an assessment inquiry.

For blockchain systems, private systems, confidential evidence, unusual complexity, or a scope that does not fit one of the fixed services, define the target and question before sending material.