One platform, many products, each in its own project.
A project scopes its tests, jobs, documents, environment, repository, credentials, model and settings. Each team can connect its application without changing the platform's core.
What a project needs.
| You configure | The platform provides |
|---|---|
| a repository and a token or GitHub App | PR verdicts, issue retests, filed bugs and proposed code changes |
| how the app starts and any test patches | an environment pinned to the commit under test |
| tests in markdown or a brief for the agent | a catalog that grows from runs and explorations |
| optional application MCP servers | the agent using the app's tools alongside its screens |
| a model key or the environment default | a provider and model selected per project |
Where it stops today
- Project access is shared by signed-in dashboard users until per-project access control is added.
- A project's environment, patches and uploads must be maintained as its repository changes.
- Model credentials are shared per environment unless a project sets its own.
Questions people ask
Can several products share one deployment?
Yes. A project is the scope for everything: tests, jobs, documents, environments, repository, credentials and model choice. Products sit side by side and never see each other's data.