Enterprise private networks
Turn every approved implementation your developers create into reusable private engineering knowledge — without exposing your source code.
Choose your network mode
| Mode | Behaviour | Disclosure |
|---|---|---|
| Private only | Internal sources only | No external disclosure · no public imports |
| Private then public | Internal first | Developer approval before sanitised public search |
| Federated | Automatic external | Policy-approved external search · source code blocked by default |
| Collaborative | Approved sharing | Search, imports and human-approved publication |
Design a network
Design your network
Front-end demonstration- Connected private GitHub
- Public GitHub search
- Public PatchMesh search
- Allow outbound source code
- Allow outbound embeddings
- Require import quarantine
- Allow public publishing
Resulting policy
Private knowledge, public discovery
Search public sources with sanitised metadata; import to quarantine; no outbound code; no publishing.
Source code outbound: blocked · Publishing: blocked
Enterprise boundary
Inside the enterprise boundary
Developer A cache
Developer B cache
Connected private GitHub
Enterprise capsule index
Enterprise artifact store
Enterprise validation
Policy gateway
↕ policy gatewayOptional public GitHub / public PatchMesh fallback — only with sanitised metadata.
What you get
- ✓ Private engineering knowledge network
- ✓ Private GitHub integration
- ✓ Tenant isolation
- ✓ Dedicated deployment
- ✓ Customer-controlled cloud / VPC pathway
- ✓ Self-hosted pathway
- ✓ Air-gapped / private-only pathway (enterprise option)
- ✓ Policy-controlled public search
- ✓ One-way imports
- ✓ Import quarantine
- ✓ Licence controls
- ✓ Approval workflows
- ✓ Audit logs
- ✓ Retention controls
- ✓ No model training on customer code
- ✓ No automatic public publishing
- ✓ Savings analytics