NDA before source code
We sign a mutual NDA before any repository, architecture document or production telemetry is shared. No exceptions, no informal previews.
Three pillars. Twelve focused engagements.
We work on systems that cannot fail quietly. Our practices are designed to make access minimal, decisions traceable and every release reversible.
We sign a mutual NDA before any repository, architecture document or production telemetry is shared. No exceptions, no informal previews.
Named accounts, short-lived credentials and managed identities. We never ask for shared administrator access to evaluate an engagement.
Cloud resources are designed for Nordic and European regions with explicit data-residency decisions documented in the Blueprint.
Code review, dependency scanning, signed container images and automated QA gates are part of the definition of done.
Centralised logs, SLO dashboards and alerting are delivered as code so your team can see exactly what the platform is doing.
Every cutover includes a rehearsed rollback path, an escalation runbook and 30 days of post-launch hypercare.
The first document is an NDA, not a sales deck. Once it is signed, we open a single secure channel and agree exactly which artefacts we may inspect. Read-only repository access is enough for the Blueprint Audit — production credentials are never required.
Mutual NDA executed before technical discovery begins
Read-only repository and configuration access for the audit
Named project channel and written decision log
Written decision log with a named owner for every change
Send your security questionnaire, threat model or vendor assessment to [email protected]. We answer from that address and can provide a completed pack under NDA. For regulatory detail, see our GDPR & cloud sovereignty page.
Start with the fixed-scope Blueprint Audit. We will show you the risk map, target architecture and a zero-downtime path forward.