Lowp tae content
Leid: SCO
Menu

Hou we rin

We rin the company onwhit we sell.

Oor beuks, specifications, bill of materials and SBOM, commercial record and email aw rin on seestems we wrate and operate. The platforms we sell rin the company first. A release that wad brak a set o beuks braks oors afore onie ither bodie's.

production databases, ilk ane awned bi ae service
22
database hosts
4
countries
3
minutes recovery point on the managed fleet, at maist
5

Comparison

Whit we uise for ilka concern

We rin the systems ahint thir records oorsels an are accoontable whan a record is wrang.

ConcernUsually bocht inWe rin
The beuksA subscription tae accoontsLedger
Specifications and chynge controlA hostit issue trackerTracker
Bill o materials and SBOMA spreadsheet, gin onythingProvenance
The commercial record (CRM)A sales subscription, separate frae the accoontsTrace
Documentation and runbooksA documentation subscriptionKnowledge base
Company emailA mail and office subscriptionWabmail

Aw the systems abuin are biggit, deployed an runnin on databases o their ain. Checkit 2026-09-09.

The systems

The sax seestems

Oor seestems cover ane concern apiece, sign fowk in throu oor ain identity service and export data in open formats frae separate databases.

  • The beuks

    Ledger

    Double-entry accoontin for siller, credits an stock. It keeps oor buiks an is the service we sell.

    Biggit on
    Auth, PostgreSQL
    Data available as
    CSV and JSON

    Opent Ledger Ledger product page

  • Specifications and chynge control

    Tracker

    Chynges tae wir repositories stairt wi a written specification an a ticket, an end wi a note o hou they war verified.

    Biggit on
    issuedb-cli + EARS, Identity
    Data available as
    JSON, and the ticket database committed in ilka repository

    Opent Tracker

  • Bill o materials and SBOM

    Provenance

    A asset register for the hardware, an SBOM for ilka software release we ship, an security findings trackit agin baith.

    Biggit on
    Auth, PostgreSQL
    Data available as
    CycloneDX, SPDX and VEX

    Opent Provenance Provenance product page Sign-in required

  • The commercial record (CRM)

    Trace

    Custmer relationship an revenue records, reconciled again the ledger.

    Biggit on
    Ledger, Auth
    Data available as
    CSV and JSON

    Opent Trace Trace product page Sign-in required

  • Documentation and runbooks

    Knowledge base

    Documentation for the platforms athort the hale seestem, includin the runbooks for oor services.

    Biggit on
    Auth, TokenGate
    Data available as
    Markdown and JSON

    Opent Knowledge base Sign-in required

  • Company email

    Wabmail

    A mailbox interface ower wir ain mail platform that keeps company correspondence on infrastructur we operate.

    Biggit on
    RODMENA Mail API, Identity
    Data available as
    IMAP and mbox

    Opent Wabmail Sign-in required

Inby

The Provenance register

Fower screens frae Provenance: the hardware asset register, the evidence pack organised by control reference, the findings table wi VEX positions, and the component explorer.

Fower screens frae the Provenance bill-o-materials platform. An asset register that leets ilka device the company hauds wi its state, custodian and encryption status. An evidence export pack organised by control reference, wi sections for Cyber Essentials and for ISO/IEC 27001:2022 Annex A, ilkane statin whit the register evidences and whit it disna. A findings table that leets vulnerabilities by severity wi their CVSS score, the component and release affected, whether that release is deployed, and its VEX assessment. A component explorer that looks a component up across the hale estate by package URL.
Provenance, oor bill-of-materials platform, in uiss. We biggit it for the evidence pack. Whan a buyer speirs whit components a release hauds and whit advisories affect thaim, we answer wi an export.

Big or buy

Why we bigg oor ain

For maist o thir seestems, buyin ane in wad mak little sense.

  • We sell it awready

    The ledger that keeps wir buiks is ane o the products on this steid. Peyin oniebody ither for an equivalent wad be unco, an rinnin it wirsels shaws us whit a release dis tae a wirkin set o buiks.

  • A register for oor ain estate

    We wantit a component inventory an security findins for wir ain estate in CycloneDX, SPDX an VEX, unner wir ain control, an biggit a register tae haud them.

  • We uise staundart foundations

    Awthing abuin rins on PostgreSQL, FreeBSD, Python, OpenID Connect an TLS wi public trust. We write the application layer but no wir ain databases, operating systems or cryptography.

Risk frae key-person

A company that rins its ain seestems haes tae thole the fowk that biggit thaim bein awa. Oor repositories hae runbooks, and chynges hae a specification and a ticket that records hou they war verified. Database migrations are stored inside the database they manage and survive a restore wi it. We test restores end tae end, and a published topology descrives the haill seestem-estate.

Hou we secure it Hou ye leave Trust Centre

Dependencies

Whit ilka system is biggit on

The raws shaw a concern, the system that handles it, an the platforms frae oor ain catalogue that it rins on.

  1. The beuks

    Ledger

    Auth, PostgreSQL

  2. Specifications and chynge control

    Tracker

    issuedb-cli + EARS, Identity

  3. Bill o materials and SBOM

    Provenance

    Auth, PostgreSQL

  4. The commercial record (CRM)

    Trace

    Ledger, Auth

  5. Documentation and runbooks

    Knowledge base

    Auth, TokenGate

  6. Company email

    Wabmail

    RODMENA Mail API, Identity

The richt-haund column comes frae oor ain product catalogue. We uise the platforms we sell tae invoice, ship an keep oor records. See hou the platforms fit thegither.

Arrange a walkthrough

We can tak ye throu ony o thir seestems, or send the topology, policies and capability statement for yer procurement pack.

Conneck wi us Statement o Capability (PDF)