Questions we can answer now.
Where a fact is not settled — registration, regions, a public rate — the answer says so.
What size of engagement do you take on?
Three ways to start: a 1–2 day workshop, an assessment of about two weeks, or a 4–6 week proof of concept. A production build is scoped only after a proof has a go decision.
Where do you operate?
Remote, and on-site when the engagement needs it. The contracting entity and the delivery region are confirmed on the first call. They are not printed here until the registration details are ready to publish.
Which models do you use, and can we bring our own?
Yes. Work runs in your tenant, on a model we agree, including one you already operate. Product names are written into the proposal. They are not a standing badge on this site.
Can it run in our tenant or on-premises?
Yes. The default is your cloud tenant or a private endpoint. On-premises is in scope when the systems require it. No client data is sent to a public model without written approval.
Is our data used to train models?
No. Not public models, and not a shared pool. If a later engagement needed anything else, it would be a separate written decision, not a default.
Do you sign NDAs?
Yes, on request, before detailed systems or data are discussed.
What happens after the proof of concept?
A go or no-go against the baseline. A build after that is its own engagement: the production system, documentation, handover, and support. We do not slide from a pilot into an open-ended team.
Who owns the code and the IP?
You own the deliverables made for you. AegisOps keeps its pre-existing tools, generic components, and know-how. The statement of work repeats this before work starts.
Who will work on our project?
A named senior lead, from the first call to handover. Specialists from the vetted network are labeled on the proposal. They are associates, not staff we forgot to mention. One contract, with AegisOps.
How do you use AI in your own delivery, and how is that work reviewed?
Agents draft analysis, code, tests, and documentation. Engineers review what they produce. Review means code review, automated tests, and security scanning. Client data does not go to a public model without approval.