MODELS & DEPLOYMENT

Your models and infrastructure
One engineering process

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 work

01 · SEPARATE THE CHOICES

Choose the setup around the work

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.

Models

Use compatible connections

Connect a supported provider endpoint or a compatible model you operate. Keep the choice in your team’s configuration.

Profiles and workflows

Define permitted approaches

Set the model, reasoning depth, instructions, and tools for different kinds of work.

Execution

Choose the environment

Use hosted execution or customer-hosted execution that connects to the managed coordination service.

Inspect the specification profiles

02 · FOLLOW ONE TASK

The environment changes
The shared process carries through

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.

Customer-hosted execution path

Your tracker

Issue, team decisions, and agreed outcome

GenieWorks

Managed coordination, task queue, project context, and encrypted credentials

Your environment

Workflow execution, compatible models, and your compute

Results and usage return to the managed service and shared team history

03 · MAKE OWNERSHIP EXPLICIT

Customer-hosted execution
Managed coordination

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.

Deployment responsibilities
ResponsibilityHosted executionCustomer-hosted execution
Workflow executionGenieWorks environmentYour environment
Model connectionSelected compatible providerSelected compatible provider or model you operate
Task coordination and queueManaged by GenieWorksManaged by GenieWorks
Encrypted credential storageManaged by GenieWorksManaged by GenieWorks
Results, usage, and run recordsReturned to the managed serviceReturned to the managed service

04 · RETURN THE RESULT TO THE TEAM

The work stays shared when a laptop closes

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.

A SHARED TEAM CAPABILITY

Built for products people depend on

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.

Your model choicesYour execution environmentShared team contextInspectable work

CONTINUE THE WORK

Bring your setup into the conversation

Discuss your models, connectivity, and execution requirements. Work out the deployment boundary your team needs.

Trackers and MCP connections
Discuss your deployment

Silent visual walkthrough · Narration shown above