Controlled model exposure
Expose approved Odoo-side models through a governed bridge instead of publishing private model authority content or relying on ad hoc metadata exports.
Commercial Odoo Integration
Governed Odoo model access for MCP and AI workflows.
Foggy Odoo Bridge Pro is a private commercial bridge for teams that need to expose approved Odoo models to Foggy MCP consumers without turning internal authority assets into a public repository. The product focuses on edition-aware packaging, runtime-aware model availability, and support-ready delivery.
Private commercial edition
Odoo 17 baseline
English default, Chinese available
What Customers Are Buying
This product is for organizations that want controlled Odoo model exposure instead of a loose export. It is positioned for private delivery, operational support, and governed integration into MCP-facing or AI-assisted workflows.
Commercial private delivery
Keep protected capabilities in a private commercial line while still offering a public-facing support, privacy, and product entry point for marketplace listing and customer review.
Deployment-aware behavior
Align visible models and metadata behavior with the real Odoo runtime so optional apps and edition boundaries remain explicit instead of drifting over time.
Current Commercial Baseline
The points below are phrased as current baseline capabilities. Planned items are separated later on this page so the public description stays accurate.
Edition-aware packaging
- Maintains explicit community and pro boundaries in the documented manifest baseline.
- Supports protected delivery paths for non-public commercial capabilities.
- Avoids mixing public-facing metadata with private authority-source ownership.
Runtime-aware availability
- Respects installed Odoo modules instead of assuming every optional app is present.
- Treats optional applications such as
mrpandprojectas deployment-dependent. - Applies final guardrails to visible models and metadata fallback behavior.
Governed distribution
- Fits a bundle and lock based distribution model rather than source-copying from the authority side.
- Supports downstream consumers that need stable, repeatable delivery semantics.
- Works with private commercial delivery instead of forcing public repository exposure.
Engineering baseline
- Workspace records a documented 475-test passing baseline.
- Recorded version baseline:
17.0.1.6.0. - Migration scripts are part of the documented delivery baseline.
How Delivery Works
Customers should evaluate this as an integration product. It is not marketed here as a self-contained public addon that runs without surrounding services.
1. Odoo side
The bridge line is installed against the customer Odoo environment and works with the real set of enabled modules and edition boundaries.
2. Foggy side
Foggy MCP or gateway components consume the governed output, preserving the bridge as the decision point for model visibility and packaging boundaries.
3. Consumer side
AI assistants, tools, or downstream integrations consume the exposed model surface through the supported MCP or gateway path.
External services are part of the offer
If your deployment requires Foggy MCP service components, gateway wiring, or customer-specific configuration, that dependency is part of the commercial integration scope and should be evaluated up front.
Commercial Positioning
This public website is meant to explain the product clearly enough for marketplace review and customer qualification, while keeping private implementation details out of the public surface.
Suitable customer profiles
- Organizations exposing selected Odoo models to AI or automation flows.
- Teams that need edition-aware and runtime-aware integration behavior.
- Partners that want private commercial delivery instead of public source disclosure.
Public site responsibilities
- Describe the product accurately.
- Disclose required external-service dependencies.
- Provide support, privacy, and terms entry points.
- Avoid claiming roadmap items as current guaranteed functionality.
Where It Fits Best
This product is strongest when customers already know they need governed model exposure, private delivery, and integration-aware rollout instead of a generic addon install.
AI-assisted internal operations
Use approved Odoo models inside assistant or automation workflows without opening the entire ERP surface to uncontrolled consumers.
Governed enterprise rollouts
Keep edition boundaries, optional apps, and runtime availability explicit when multiple teams or environments share the same integration line.
Private partner delivery
Support customer delivery without forcing private bridge logic into a public source workflow or a public marketplace artifact.
Typical Evaluation Path
Commercial qualification usually starts with scope confirmation, then deployment boundary review, and only then delivery planning.
1. Scope the target models
Identify which Odoo models, modules, and business flows need to be exposed to MCP consumers.
2. Review the boundary
Confirm edition separation, optional-module behavior, deployment mode, and any required Foggy-side service components.
3. Plan rollout
Decide delivery path, support channel, and rollout steps for test, staging, and production environments.
Request a demo or integration review
Email support@foggysource.com with your Odoo version, target modules, and intended MCP or AI use case. This helps us keep the first discussion concrete instead of generic.
Planned Roadmap
The items below come from accepted workspace planning and are intentionally marked as planned rather than sold as current default guarantees.
Field-level visibility boundaries
Introduce visible-versus-blocked field governance, with bridge-side decision logic and downstream enforcement support.
Separated metadata channels
Split user-facing metadata filtering from internal system-facing metadata loading so governance can be tightened without breaking internal mapping paths.
Masking and export governance
Extend governance into masking, audit trails, prompt narrowing, and export-related inheritance decisions.
FAQ
Is this a standalone public addon with no external dependencies?
No. This product should be evaluated as a commercial integration bridge and may require Foggy MCP or gateway components in addition to the Odoo-side delivery.
Does this page describe only current features?
Current capabilities and planned roadmap items are separated on purpose so the public description remains accurate and reviewable.
Can I request support before purchase or rollout?
Yes. Use the support page to open a qualification, deployment, or privacy-related inquiry.
Is Chinese information available?
Yes. A Chinese mirror is available from the language switch in the header and footer. English remains the default public entry point.