01
Policy
Data residency, approved providers and models, fallback, approval before card-billed capacity and budget ceiling.
Deployment / pilot assessment
Deployment starts with your data and operating boundary
Gyde defines where requests, weights, logs and operational access may go before selecting infrastructure. The currently proven managed prototype runs in one geography. A customer-cloud or customer-site arrangement is a design and validation exercise, scoped to the buyer's environment.
Current supplier tests and managed prototype: one geography. Other regions require provider checks and a customer-specific pilot.
GYDE / INFERENCEILLUSTRATIVE PILOT FLOW
DESIGN PATH / BUYER-SPECIFIC
01WorkloadTask + test cases
02ModelQualified candidate
03PolicyAllowed route
04ServingApproved capacity
05EvidenceOutcome + cost
Decision: proceed, redesign or stop
01Start with the boundary
Map every data path before infrastructure selection.
For each asset, the pilot records location, controller, access, retention and a validation method. The entries below are design questions, not configured defaults.
| Asset | Location and access to agree | Validation |
|---|---|---|
| Ingress and gateway | Country, region, operator, identity and network path | Route and egress check |
| 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 | Policy block and egress test |
02Boundary path
Verify the full route, not only the GPU region.
This is a proposed pilot boundary map. The customer and Gyde record the actual location and operator for each stage before traffic is enabled.
01Ingress→︎
02Approved gateway→︎
03Approved GPU path→︎
04Metadata record→︎
05Retention and deletion
03Deployment profiles
Managed pilots are tested; customer installs need validation.
| Mode | What a buyer can request | Current state |
|---|---|---|
| Gyde-managed pilot | Bounded workload under agreed location, provider and data rules | Prototype demonstrated in one geography. Production terms, controls and availability remain to be agreed. |
| Customer-cloud pilot | Design in the buyer's account, network, identity and approved region | Proposed profile. Packaging and deployment acceptance are incomplete. |
| Customer site | Infrastructure design and commissioning | AI Lab Infrastructure consulting exists. A Gyde Inference on-premise installer does not. |
04Control checklist
Set the rules for data, spend and operation.
02
Security
Key ownership, identity, private network, egress, content logging and retention or deletion.
03
Operations
Monitoring, incident response, failure drill, rollback, request accounting and billed-cost reconciliation.
05Pilot template
Assign responsibility before traffic starts.
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
Test the boundary in the proposed environment.
The deployment review checks egress, region, provider inventory, failure handling, request accounting, secrets, and restore or rollback. On-site infrastructure work is available separately through Gyde's AI Lab Infrastructure consulting.
Explore infrastructure consulting?Buyer questions
Questions to settle before a pilot.
Answers reflect the current prototype and scoped engagement approach.
Can Gyde run in our cloud account?
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.
Can we keep payload-bearing data in a chosen region?
The requirement must be mapped across ingress, gateway, serving, logging, backups, support and any fallback path, then verified for the proposed deployment. Current proof is geography-specific.
Is on-premise supported?
Gyde offers AI Lab Infrastructure consulting for customer-site design and commissioning. A Gyde Inference on-premise product installer has not been built.
Who approves GPU spend?
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
Start with a workload you can measure.
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.