Industries · Telecommunications
Network knowledge is critical infrastructure. Treat it that way.
Northwood deploys and operates Oak for telecom operators: chat, search and agents over network procedures, incident history and customer operations, inside your perimeter.
Why it matters
Your network security team is right.
Operators run on knowledge that maps their own network: topology, configurations, maintenance procedures, incident reports, vendor documentation and customer records. That’s exactly the context an attacker would want, and it shouldn’t sit in someone else’s cloud.
Northwood deploys Oak inside your perimeter, with outbound traffic limited to an allowlist and a record of every question.
Use cases
Where telecom operators put Oak to work.
Procedure assistantAnswer questions from maintenance procedures and vendor manuals, citing the controlling document and revision.
Incident drafterDraft incident timelines from log excerpts and runbook references, reviewed before publication.
Change reviewCheck a proposed change against your standards and past incidents, and flag conflicts before the window.
Customer operations knowledgeGive care teams cited answers on plans, policies and known issues.
Controls
What stays true in every deployment.
Outbound traffic is restricted to an allowlist. Off-list calls fail closed, logged and alerted.
All compute, storage and routing is in your environment. No shared cluster.
Sensitive workflows require a named approver.
Deployment
Your cloud, your servers, or no connection at all.
Your cloudOak runs in your own cloud account, next to the data it reads.
Your serversRun Oak on hardware you own, in your data centre or your office.
Fully air-gappedNo outside connection. Models, search and logs all run locally.