Start a conversation

Standards

Built to be looked after

Connected software is only as good as your ability to see what it is doing. These are the standards we hold, and where they stop.

Corten steel and glass facade of a modern office building

Standard

Observability

Every workflow writes a readable log: when it ran, what it read, what it wrote, what it rejected and why. Portals record significant user actions. Your team can answer “did it run, and what happened?” without calling us.

Standard

Designed failure

For each connection we document what happens if the source is unavailable, the target rejects a record, a credential expires or a file is malformed. The default is to pause safely, keep what was already processed, and alert a named person.

Standard

Security habits

  • Dedicated integration accounts with minimum permissions
  • Secrets held in the hosting platform’s secret store, never in code
  • Dependencies kept current and reviewed
  • Personal data limited to fields a process actually uses

These are working habits, not a certification. If you need an independent assessment, we will prepare for it and remediate findings.

Standard

Accessibility

External portals and internal tools are built for keyboard use, screen readers, sufficient contrast and clear error messages, checked against WCAG 2.2 AA success criteria that can be tested without specialist assistive technology audits.

Standard

Documentation

A connection map, data agreement, run book and architecture note for every engagement, kept in your repository and updated as things change.