Connect IOModel with IDEs, CI pipelines, repositories, and contract tooling for an end-to-end delivery loop.
IOModel fits into your existing toolchain. For file-based Git-projects, your repository, IDE, and CI are the integration points; contracts like OpenAPI live as attachments in the model. Native cloud connections build on top of that foundation.
Integration surfaces
File-based Git-projects integrate through Git and CI. Cloud projects add native Git sync (GitHub or GitLab, bidirectional branch sync), and webhooks automate validation and downstream actions on model changes.
In this section
GitHub Connection
Work with IOModel content in a GitHub repository.
GitLab Connection
Work with IOModel content in a GitLab repository.
Webhook and Automation
Automate validation and downstream actions.
What integrates today
| Surface | How |
|---|---|
| Editor | VS Code / Cursor extension |
| CI | CLI validation in pipelines |
| Repository | Git-project files in GitHub/GitLab |
| Cloud sync | GitHub and GitLab for cloud projects (plan feature) |
| Contracts | OpenAPI attachments embedded in specs |
If your team already reviews code in Git, keep architecture there too. The repository becomes the single integration point for editor, CI, and review.
Last updated on