Talk to our engineering-led sales team
AegisWire engagements begin with architects, not sales pitches. Our first conversation is a working session: we map your transport, trust, policy, and compliance boundaries against the platform, and answer technical questions directly. Deployments are scoped per environment, contracted annually, and delivered with a named account team.
Request a briefing
Typical first response within one business day. Submissions are routed to a named Solutions Engineer based on industry and region.
Direct contact
What to expect next
- 1 Discovery call — 30–45 minutes, engineering + solutions. Map your environment, constraints, and compliance posture.
- 2 Architecture briefing — deep-dive against your reference architecture. NDA-friendly; ask anything.
- 3 Proof of concept — scoped, time-boxed, in your environment with your identity provider and policy set.
- 4 Commercial — MSA, DPA, SOW, and SLA. Invoice-based annual terms. Procurement-standard paperwork.
- 5 Delivery — named Solutions Engineer, named Customer Success, named incident hotline.
Who we engage
Registered entity
AegisWire is operated by ITLOX LTD, registered in England & Wales. Deployments are supported globally; primary regions include UK, EU, North America, Middle East, and APAC.
Built for procurement and security review
We arrive at the evaluation table with the evidence a serious buyer needs to pass internal committees.
Post-quantum by default
Hybrid Kyber + classical key agreement on every session. No legacy-only path.
Procurement-ready
MSA, DPA, sub-processor list, SLA, SOC-2-aligned controls, audit evidence package.
Deployment flexibility
BYOE, hosted, on-prem, hardware appliance, air-gapped. Same verified artefacts everywhere.
Named account team
Solutions Engineer, Customer Success, incident hotline — assigned for every engagement.
Frequently asked — procurement edition
The questions that come up in every enterprise evaluation cycle. Answered up front.
Why is there no public pricing page?
Serious deployments are shaped by named users, deployment model, regions, retention, compliance posture, identity integration, and support tier — not by a self-serve checkout page. We quote per engagement. Our commercial lead will share a written proposal within the first week of conversation, bounded by a published pricing methodology you can share with procurement.
Do you offer a proof-of-concept?
Yes. POCs run in your environment with your identity provider, your policy set, and your compliance controls — typically 2 to 6 weeks with jointly agreed acceptance criteria. We provide Solutions Engineering throughout. There is no charge for a scoped POC on a path to a commercial engagement.
MSA, DPA, and sub-processor list — available?
Yes. Standard MSA, DPA (including UK IDTA and EU SCCs), and sub-processor list are available under NDA. Customer-paper MSAs are accepted for larger accounts with reasonable amendments. DPIA input and legal review support is provided as part of the procurement package.
Can we deploy in our own cloud account or on-premises?
Yes. BYOE (Bring Your Own Environment) is our primary enterprise motion — AegisWire deploys and operates the platform inside your AWS, Azure, or GCP account. On-premises, hardware-appliance, and air-gapped / sovereign deployments are supported for customers with data-residency or classification requirements. See the deployment models page for detail.
Which identity providers and directories do you integrate with?
SAML 2.0 and OIDC — Entra ID, Okta, Ping, Google Workspace, and any standards-compliant IdP. SCIM 2.0 for provisioning. mTLS and FIDO2 hardware-key binding for strong device authentication. Custom IdP integration is scoped during the discovery call.
How is data stored, and where?
For BYOE and on-prem deployments, data stays in your environment — AegisWire has no access to session or policy data. For hosted deployments, data residency is selected at contract time from supported regions. Encryption at rest and in transit is default-on everywhere. See the Trust Center for details.
What is your billing and contracting model?
Annual invoice-based, NET 30 / 60 / 90 available, multi-year pricing locks on request. Purchase-order and standard procurement processes accepted. No credit-card self-serve for enterprise plans. Marketplace transactions (AWS, Azure) available on request for pre-committed cloud spend.
What SLA do you offer, and what happens on breach?
Availability, response-time, and resolution-time targets are contracted per tier with service credits on miss. Our published Service Level Agreement is the baseline; enterprise engagements typically uplift to a dedicated SLA with named incident contacts and a 24×7 escalation path.
Can we see architecture documents, source-code provenance, and build attestations?
Yes. Under NDA we share full architecture documentation, threat models, software bill of materials (SBOM), reproducible-build attestations, signing-key provenance, and audit evidence bundles. For regulated customers, source-code escrow arrangements are available through a third-party escrow agent.
Ready when procurement is.
We deliver the engineering artefacts, commercial paperwork, and deployment assurance your security committee expects — on the first call.