01
People & permissions
Give every member a clear role in your organization.
YOUR SOFTWARE COMPANY. CONNECTED.
Bring your company together.Command every workload.
Unite your team, client environments, and intelligent workflows into one governed cockpit.
Odoo ERP & Enterprise CoreSeparate organization productsGoverned MCP Agent Runtime
Your organization. Your tools. Your way of working.
Flow:1 / 3
Steps:0 / 5
Mode:Illustrated
CODE EXAMPLEREADY
tc-cli>
THREE CONNECTED CONTROLS
People, projects and systems. In context.
A shared starting point for developers, consultants and the people who run their software.
3D Camera Depth 🎮35%
●People
ORBIT_01Members, roles, account settings and support — organized around your company.
TEAM ROLESACCESS SETTINGS
●Projects
ORBIT_02Project context, repositories, workspaces, reviews and delivery — connected across the team.
CHANGE REVIEWSGIT CONNECTIONS
●Systems
ORBIT_03Servers, application workloads, AI providers and tool connections — managed in context.
MCP TOOLSCONNECTED SERVERS
Drag 360° Orbit / Wheel to Zoom
ORBIT_01 // PEOPLE & ACCESSZOOM: 12.0 | YAW: 0.60 | PITCH: 1.15MOTION PAUSED
Connected controls
Areas of work
AI provider options
One organization portal, with features and permissions tailored to your team.
CONNECTION OVERVIEW
How your organization connects
Explore how an organization domain connects to its automation product and data.
An illustration of access to an organization’s product, not a connection test. Odoo systems and development workspaces run on the organization’s connected servers unless a specific platform-hosting exception is granted.
💻
Client Browser
alpha.example.com
🔀
Domain routing
Secure access over HTTPS
🐳
Organization automation product
Alpha organization product
🗄️
Dedicated Database
Alpha organization data
// CHANGE REVIEW & POLICY GATES
Branch Governance & Policy Review Simulation
Explore approval and requested changes before a release reaches its target environment.
Explore a change-review example. This does not inspect code or deploy a release.
🌿 dev/feature-payroll
The developer prepares changes on a working branch and opens a pull request for review.
🛡️ staging (Change Review Gate)
The reviewer checks changes and required results according to project settings and team permissions.
🔒 main (Production Release)
After approval, follow the project’s release steps and deployment requirements.
GETTING STARTED
A clear path from request to setup.
Choose your plan, set up your organization and bring your team and tools into a shared workflow.
- 01Selected step
Request access
Choose a published plan, provide your organization details and review the available agreements.
- 02Explore this step
Complete review
Follow account verification and application review. More information may be needed before approval.
- 03Explore this step
Set up your organization
After approval, configure your portal, invite your team and assign appropriate roles.
- 04Explore this step
Connect at your pace
Add projects, supported server connections and optional AI settings. Verify each integration before using it.
INSIDE YOUR ORGANIZATION
The whole workflow. In view.
From account setup to development and operations, explore the areas that connect your work.
02
Projects & repositories
Bring project context, GitHub accounts and repository branches together.
03
Development workspaces
Keep development work connected to its project and source.
odoo_models/account_payment.py
def action_confirm_payout(self):
# ORM example; business rules still require review
return self.filtered(lambda r: r.state == 'draft').write({'state': 'posted'})An ORM illustration, not production-approved code.
04
Reviews & delivery
Follow a change from review through approval and delivery.
05
Servers & applications
Discover workloads on connected servers and organize the systems you manage.
06
Operations & recovery
Keep actions, their outcomes and follow-up work in one traceable process.
07
AI on your terms
Choose models and providers with policies that fit your team.
08
MCP connections
Organize tool connections and their access within the right account.
Scoped MCP BoundaryConfigured permissions
Connection credentials belong in their designated settings. Administrators control available tools and access.
09
Usage & accountability
Understand activity, allowances and AI consumption in context.
10
Your organization portal
Keep account administration and team work connected, but distinct.
Activity record example
EXAMPLE: select to explore an activity record
SECURITY AND RESPONSIBILITY
Make access deliberate. Keep actions accountable.
Define access by role, check readiness before sensitive actions and keep decisions traceable.
Organization-scoped access
Access checks use organization membership and role permissions. Platform administration and organization work are separate areas.
Checks before changes
Remote operations are limited to supported actions and require the relevant permissions and readiness checks.
Separate credentials
Discovery and remote write operations use separate credentials. Grant only the access needed for each task.
Recorded outcomes
Operation records distinguish confirmed results from failures and outcomes that still need investigation.
OPTIONAL AI
Your models. Your policies. Your context.
Combine organization providers, permitted personal connections and shared models in a policy-driven setup.
Organization connections
Keep provider settings under your organization’s control, subject to your plan and AI policy.
Personal connections
Allow individual provider settings only when both the organization policy and plan permit them.
Shared model grants
An operator can allocate selected platform models to an organization with explicit limits. A grant does not enable unrestricted access.
Track tokens and estimated costs alongside model access. Provider charges and data policies remain specific to each connection.
Your tools, connected
Choose a connection. Understand its role.
TrineContext & permissions
Projects & repositories
Bring project context, GitHub accounts and repository branches together.
- Project catalogue
- Repository connections
- Branches and revisions
Before you get started
Is ThreeControl only for Odoo teams?
No. Organization and project management are for software teams in general. Runtime discovery and operations support specific environments; confirm support for your systems before onboarding.
Can I connect an existing server?
Yes. Connect a supported server, discover its workloads and verify access before enabling management. Connection options depend on how your applications are installed and reached.
How do plans and organization setup work?
Choose a published offer and submit your organization details. Follow the account review and setup steps, then invite your team and configure your connections. Features and allowances follow your subscription.
Do I need an AI subscription?
AI is optional. You can configure organization providers, permit personal connections or use models allocated through your plan. Organization policies determine what members can access.
PLANS
Choose the scope that fits your team.
Compare features and allowances, then choose the plan that fits your team.
Matching plans: 1
Closed pilot
Invitation-only technical trial for projects, tasks and workflows. Manual support; no payments, AI or managed workload hosting.
$0.00per month
Trial up to 14 days from approval. No automatic renewal.
- Included seats: 3
Closed pilot
Invitation-only technical trial for projects, tasks and workflows. Manual support; no payments, AI or managed workload hosting.
$0.00 / month
Free trial up to 14 days from approval. No automatic renewal or charge.
- AI assistance
- Development workspaces
- External connections
- Team seats
- 3
- Concurrent runs
- 0
- Storage (GB)
- 5
- Monthly AI tokens
- 0
Offer revision 1
Request access| Plan | Closed pilot |
|---|---|
| Price | $0.00 / month |
| AI assistance | — |
| Development workspaces | — |
| External connections | — |
| Team seats | 3 |
| Concurrent runs | 0 |
| Storage (GB) | 5 |
| Monthly AI tokens | 0 |
Features and allowances follow the selected offer. External AI providers and hosting may carry separate charges.
The subscription hosts the automation management product. Odoo systems, development workspaces and builds require your own external server at your expense; platform workload hosting is not included.
The subscription hosts the automation management product. Odoo systems, development workspaces and builds require your own external server at your expense; platform workload hosting is not included.
Start with your team’s needs.
Review the available plans or ask us whether your setup is supported.
Contact