Secure intake
Tell us what needs building, checking or fixing.
Describe the system, the question and the timing. That's what we use to talk through the work and write a scope. Detailed records, credentials and physical devices are handled separately, after we've agreed how.
Information to prepare
Six details that help us understand the request.
- Workflow description
- Tools and integrations
- Data classes
- Decision deadline
- Desired deliverable
- Access and sensitivity notes
Request details
Describe the project
This form drafts a message for the contact page, where you can review it and add your details before sending. Keep confidential material out of both.
01
What to include
- The business decision the work has to support.
- The system or the question: an AI workflow, an architecture, security controls, identity, a device, firmware, an incident, a briefing.
- Tools, integrations, data classes and environments, at a high level.
- Timeline, who's involved, and what you need to end up with.
02
What not to include
- No secrets, credentials, tokens, API keys, regulated data, customer PII, payloads, confidential firmware images or files. Don't ship a physical device before we've agreed how to handle it.
- If you'll need a secure path for sensitive material, say so in the first message and we'll set one up.
Related services and resources
Next step