Engineering leadership
- Assistant rollout without a per-tool compliance review
- Model choice revisited on price and quality, not on vendor lock-in
Second wave
Completions and refactors without exporting the repository
Source code is often the most jurisdiction-sensitive asset an engineering team holds, and the hardest to keep in one place when developer tooling defaults to global endpoints.
- Per-key
- Boundary isolation
- OpenAI-compatible
- Endpoint surface
- Overview
- Coverage
Code separate from chat
Written at second wave
01
The problem
Editor traffic outside the gateway
Failure mode 01
Assistant traffic may bypass the gateway used by the rest of the stack.
Failure mode 02
Context windows drag large slices of a repository into every request.
Failure mode 03
Inline completion latency may encourage pinning a single provider.
02
The approach
Editor integration
Measure 01
An OpenAI-compatible endpoint points any editor or harness at Menu Items without plugin changes.
Measure 02
Repository-scoped keys keep a code boundary separate from a chat boundary.
Measure 03
Fast paths are selected inside the region rather than across it.
03
Models for this workload
Starting points and serving regions
| Model | Provider | Context | Input, per 1M | Regions | Residency |
|---|---|---|---|---|---|
| DeepSeek V4 Pro | DeepSeek | 1M | $0.3 | CN · cn-beijing | In region |
| Kimi K3 | Moonshot AI (Kimi) | 1.05M | $3.00 | cn-beijing · cn-hongkong | In region |
04
Who this is for
Audience
Developer experience
- Existing plugins keep working
- Latency preserved inside the boundary
Security
- One egress path to review
- Key-level controls over what may be sent where
05
Other solutions
Other solutions
01
Enterprise RAG
Retrieval for data that must stay in the country
02
Multimodal
Images, audio and video under text's rules
03
Agentic systems
Long tool loops that stay inside a jurisdiction
05
Second waveConversational AI
Streaming assistants with residency that holds under load
06
Second waveSearch
Ranking and reranking inside the same boundary as model output
Describe a different workload
Start