Oryntis

Practice

A forecast you can hold us to.

These standards apply to every project. They are specific on purpose, so you can check them.

Scope

A written scope before work begins, covering purpose, users, inclusions, exclusions and risks. Changes logged with their effect before they start.

Communication

One written note per week. Calls when useful, always summarised in writing afterwards.

Working software

Builds you can open yourself at least every two weeks during active development.

Infrastructure as code

Environments defined in reviewable files so they can be recreated, compared and audited.

Testing

Code review on every change, automated tests on important behaviour, and real-device checks before release.

Backups and restores

Backups encrypted and stored separately, with restore tests on an agreed schedule.

Accessibility

WCAG 2.2 AA target, checked with keyboard, screen reader, zoom and contrast tools.

Security basics

Least-privilege access, multi-factor sign-in, secrets out of code, updates applied. Not a certification.

Handover

Code, cloud and store accounts in your name; documentation and a walkthrough at the end.