Use compatible connections
Connect a supported provider endpoint or a compatible model you operate. Keep the choice in your team’s configuration.
MODELS & DEPLOYMENT
Use your preferred compatible models, choose where execution runs, and keep the work inside your team’s tracker. GenieWorks carries the engineering workflow around those choices.
Follow the work01 · SEPARATE THE CHOICES
Model capability, the engineering method, and where execution runs are separate decisions. Your team can configure them together without moving the workflow into someone’s personal session.
Connect a supported provider endpoint or a compatible model you operate. Keep the choice in your team’s configuration.
Set the model, reasoning depth, instructions, and tools for different kinds of work.
Use hosted execution or customer-hosted execution that connects to the managed coordination service.
02 · FOLLOW ONE TASK
The tracker supplies the task. Managed coordination supplies the workflow and selected context. Execution uses the chosen model, then returns results and usage to the shared record.
Issue, team decisions, and agreed outcome

Managed coordination, task queue, project context, and encrypted credentials
Workflow execution, compatible models, and your compute
Results and usage return to the managed service and shared team history
03 · MAKE OWNERSHIP EXPLICIT
Choosing your own execution environment does not mean the entire product is self-hosted. Coordination and encrypted credential storage stay managed; results and run records return to GenieWorks.
| Responsibility | Hosted execution | Customer-hosted execution |
|---|---|---|
| Workflow execution | GenieWorks environment | Your environment |
| Model connection | Selected compatible provider | Selected compatible provider or model you operate |
| Task coordination and queue | Managed by GenieWorks | Managed by GenieWorks |
| Encrypted credential storage | Managed by GenieWorks | Managed by GenieWorks |
| Results, usage, and run records | Returned to the managed service | Returned to the managed service |
04 · RETURN THE RESULT TO THE TEAM
Teammates can see what is running, what needs input, and what finished. These product views demonstrate shared work and history; they do not prove the hosting location of a run.
Open full screenshotA SHARED TEAM CAPABILITY
This process fits teams evolving an existing product, where context, compatibility, review, and a clear definition of done matter. Early exploration that changes direction every hour is a weaker fit; team size is not the deciding factor.
CONTINUE THE WORK
Discuss your models, connectivity, and execution requirements. Work out the deployment boundary your team needs.
Trackers and MCP connections