Policy
Data residency, approved providers and models, fallback, approval before card-billed capacity and budget ceiling.
Deployment / pilot assessment
Your team can assess a managed pilot, a pilot in your cloud, or separate customer-site infrastructure work. For any path, your team and Gyde must agree where requests, model files and logs go, and who operates the service.
The managed setup has been tested in one geography. Other locations need provider and data-path checks in a pilot.
ONE WORKLOAD / PILOT PATH
01Deployment options
Choose the path that fits your data rules and operating owner. Each path has a different amount of work left before traffic can run.
| Path | What your team can assess | Current state |
|---|---|---|
| Gyde-managed pilot | One workload under agreed location, provider and data rules | Prototype demonstrated in one geography. Production terms, controls and availability remain to be agreed. |
| Pilot in your cloud | Deployment in your account, network, identity system and approved region | Proposed profile. Packaging and deployment acceptance are incomplete. |
| Customer site | Infrastructure design and commissioning through AI Lab Infrastructure consulting | A Gyde Inference on-site installer has not been built. |
02What your team must decide
Agree where requests enter, where traffic can leave, who can access each system and how long records remain. The entries below are design questions, not configured defaults.
| Asset | Location and access to agree | How to check |
|---|---|---|
| Request entry and gateway | Country, region, operator, identity and network path | Check the route and where traffic leaves the network |
| Serving GPU and model weights | Provider, host region, weight storage and support access | Inventory and region check |
| Metadata logs and backups | Content policy, retention, deletion and restore owner | Logging and deletion review |
| Third-party fallback | Explicit approval, destination and payload handling | Check blocked routes and traffic leaving the network |
03Boundary path
This is a proposed pilot boundary map. Your team and Gyde record the actual location and operator for each stage before traffic is enabled.
04Control checklist
Data residency, approved providers and models, fallback, approval before card-billed capacity and budget ceiling.
Key ownership, identity, private network, egress, content logging and retention or deletion.
Monitoring, incident response, failure drill, rollback, request accounting and billed-cost reconciliation.
05Pilot template
Ownership below is a discussion template; the signed pilot scope determines the actual split.
| Decision | Gyde | Customer | Provider |
|---|---|---|---|
| Policy and evaluation sign-off | Implement agreed controls | Own rules, source data and acceptance | Supply service constraints |
| Credentials and capacity spend | Operate as agreed | Approve account and spending policy | Bill contracted capacity |
| Incidents and deletion evidence | Run agreed response and records | Name owner and retention rules | Provide infrastructure evidence |
06Pilot verification
The deployment review checks where traffic leaves the network, the region and provider, failure handling, request accounting, secrets, and restore or rollback. On-site infrastructure work is available separately through Gyde's AI Lab Infrastructure consulting.
See infrastructure consulting?Buyer questions
That can be scoped as a customer-cloud pilot design. The current Gyde Inference prototype is not a packaged, generally available install; networking, identity, capacity and operations need acceptance in your account.
The requirement must be mapped across request entry, gateway, serving, logging, backups, support and any fallback path, then verified for the proposed deployment. Current proof is geography-specific.
Gyde offers AI Lab Infrastructure consulting for customer-site design and commissioning. A Gyde Inference on-premise product installer has not been built.
The buyer's approval policy and budget ceiling are set in the pilot. Current operations use manual approval for card-billed suppliers; the pilot agreement assigns the bill payer.
Gyde Inference pilot
Describe the task, data boundary and decision you need to make. We will scope the test and operating conditions together.
Discuss a workload Do not submit sensitive records through the marketing form.