IPv6-native direction
Prefix assignment and addressing policy are managed as controlled service records. Actual prefix source and customer eligibility are confirmed during qualification.
NETWORK / OPERATING MODEL
Overlay the world you already have.
TeraTeams separates business control from packet forwarding. Odoo coordinates the customer, contract and approved intent; dedicated network nodes carry traffic.
SYSTEM BOUNDARY
Control plane and data plane stay separate.
Odoo is the business system and control plane. It does not route customer traffic. Provisioning adapters deliver only approved configuration to the network data plane.
01Visitor & customer
↓
Needs, sites, users and support requests
02Odoo control plane
↓
CRM, contracts, TeamsBox, IPAM and overlay intent
03Approval gate
↓
Rules validation and accountable human review
04Network data plane
Tunnels, routing, forwarding and telemetry
Portable TeamsBox
A managed edge can be enrolled at the customer site while the customer-provided internet connection remains the underlay.
Health without hidden promises
Node, tunnel and service health can be summarized in Odoo. Public content does not promise an SLA until a written agreement defines one.
DELIVERY FLOW
Every change has an owner.
AI supports discovery and drafting. It cannot bypass commercial checks, address rules or production approvals.
-
01
Qualify
Confirm service country, site, access, users, capacity and intended use.
-
02
Design
Prepare an overlay and TeamsBox proposal with explicit included and excluded items.
-
03
Approve
Validate price, coverage, contract and production configuration.
-
04
Activate
Enroll the edge and record delivery evidence.
-
05
Operate
Monitor service summaries, support events and renewal dates.
Service boundary
TeraTeams does not claim universal coverage, carrier licensing or a public SLA. Availability, capacity, routing, third-party access and support terms are confirmed by written quote and agreement.
Discuss a location ↗