Confidentiality
Mutual NDAs are normal before detailed technical disclosure. We do not need your entire estate to have a first conversation; we do need a clean boundary before repositories and designs move.
Security & intellectual property
The work is yours. The access is deliberate.
Product engineering concentrates other people’s secrets: CAD, firmware, keys, customer data models, unreleased hardware. Avarix treats confidentiality, IP assignment and access as part of delivery, not a slide in onboarding.
Intellectual property
Engagement contracts specify assignment and licence. Default posture: you should own the product IP we create for you, with any background tools or libraries clearly carved out. We do not farm your device architecture as a marketing case without consent.
Access and secrets
Named accounts, least-privilege to cloud and git, no shared “admin” passwords in a chat log. Device keys, signing materials and production credentials are handled as credentials, not as attachments.
What we do not claim
We will not list SOC 2, ISO or pentest theatre we have not completed. When a program requires a specific control regime, we treat that as scoped engineering and evidence — not as a badge on this website.