Security
The customer holds the key.
When AI agents build your software, the most important question is who controls access. On Wave Engage, the answer is you.
01 · Project keys
Your project opens with your key.
Your private key is generated in your browser and never stored on our servers. The project's keys open only with a key you hold, in your browser or as a recovery key file.
02 · Code exports
Code exports need two factors.
Code exports need two factors. Exports are two-factor, single-download and recorded in the audit log. The second factor is the customer's recovery key or a different user's approval, and the requester cannot be that second user.
03 · Credentials
Agents don't hold your stored credentials.
Agents reference stored credentials only by placeholder. A separate secure service checks hard rules, written in code, before it uses the real value. Vault credentials are never handed to the agent, and the hard rules run in code outside it, so a prompt-injected agent is designed not to be able to change them.
Agent → placeholder → secure service (hard rules in code) → real value
Business requirements in. Working software out.
Custom software, guided by AI.
Nothing is built until you approve the plan and the cost.
See how it works