Tools that know your platform
Connect MCP servers. Built-in provider tools work with pull requests, reviews, and issues; Deploymate tools work with project services, logs, environments, and dependencies.
Give your coding agents a real workspace, the right tools, and a path to production. Deploymate brings your code, AI models, and running services together, with sharing and collaboration built in for your team.
import { getProjects } from './data'; export default async function Projects() { const projects = await getProjects(); return ( <ProjectGrid projects={projects} /> );}$ npm run dev
Ready · listening on 0.0.0.0:5173
Workspace preview available
Configure a Mate or Codex agent, give it repository context, and launch a session. Chat, inspect its changes, and work alongside it in the same workspace.
Connect MCP servers. Built-in provider tools work with pull requests, reviews, and issues; Deploymate tools work with project services, logs, environments, and dependencies.
Import skills from public GitHub repositories or write your own instructions. Enabled skill versions are pinned to each session.
Save and resume session snapshots. Service-backed workspaces reuse prepared development environments while keeping each session’s changes separate.
Configure MCP approval policies. Project permissions are checked when tools access services.
Choose an app event, select an agent, and give it a prompt. Add another agent when you need a second step, with the previous result as context.
Connect a Git provider and choose a supported event. Narrow the trigger with the repository, actor, and event-specific filters.
Choose an agent and write its prompt. Steps run in order, passing the event and the previous agent’s result to the next step.
Follow run history and started, finished, or failed updates. Send lifecycle notifications to your enabled notification destinations.
repository.createdInspect the repository. Summarize the architecture, setup steps, and gaps in the developer documentation.
Use the first agent’s findings to draft an onboarding checklist. Flag assumptions and changes that need review.
Use these examples to guide your agent prompts and review process. Git tools, project infrastructure, and service context are available according to permissions and tool approvals. Deployment and resource lifetimes follow their configured settings.
From an idea to a reviewed change, without losing the thread.
Open a project or repository-backed service and launch your chosen agent with its Git context.
Work through the change in chat. Inspect files, use the editor and terminals, and open the running app preview.
Review the diff, commit and push. Connected provider tools can create a pull request and add review feedback, subject to your approval settings.
Use branch-based auto deploy or explicitly deploy a commit. PR preview environments are cleaned up when the PR is merged or closed.
Jira, Asana, and ClickUp can discover accessible resources and set up webhooks automatically. Inspect incoming events and refresh hooks from Apps.
Agent automation triggers currently support mapped Git repository events. Product management events are available for collection and inspection; they do not yet launch agent workflows.
Bring model access into the same platform as your agents and applications. Configure upstream routes and connect through an OpenAI-compatible API.
Configure providers and custom base URLs, a default route, load balancing, and session-aware routing.
Create project or account gateways. Issue and revoke client keys without exposing upstream credentials to applications.
Track tokens and configure per-key token budgets and guardrails. Manage route and key settings from the dashboard.
const response = await fetch(
"https://ai-gateway.deploymate.net/v1/chat/completions",
{
method: "POST",
headers: {
Authorization: "Bearer YOUR_GATEWAY_CLIENT_KEY",
"Content-Type": "application/json",
},
body: JSON.stringify({
model: "YOUR_CONFIGURED_MODEL",
messages: [{ role: "user", content: "Let’s build." }],
}),
},
);Connect your repositories, coordinate work from your product tools, and give agents access to the tools your team uses.
Connect your code and work with repository events.
Connect task events to your agent automations.
Extend your agent’s tools with connected MCP servers.
Explore the documentationAgents are only part of the story. Deploymate also gives your team the services, storage, configuration, and operational context to run what you build.
Deploy public web services and private services from a connected repository. Choose resource plans, build/run commands, ports, and health checks.
Run background workers and cron jobs alongside your application. Keep code, environment configuration, and deployment history in one project.
Add PostgreSQL and Valkey services with persistent storage and connection details. Use them from your project’s application services and agent workflows.
Give a stateful service its own disk, or attach project volumes across workloads. Browse files, download folders, and preview supported media in the volume explorer.
Build from GitHub, GitLab, Bitbucket, or SSH. Follow a branch, pin a commit, and inspect deployment history. PR previews live only while their PR is open.
Inspect service and build logs, deployment events, CPU and memory metrics, and running pods. Open a pod terminal and configure notifications and log destinations.
Manage environment groups and secret files, attach configuration to services, and control service agent setup commands and watched dependency files.
Invite collaborators to a project or across an account. Grant Read, Create, or Write & deploy permissions; tools check access to the resources they use.
Create a Codebase for a connected repository and work with an agent before deploying anything. Review code and connect your Git provider through Apps.
Invite teammates into a project or across your account. Keep agents, sessions, and the resources behind your work accessible to the right people.
Invite people by email. Choose a single project, or grant global access to account-owned resources, including future projects and sessions outside projects.
Give collaborators access to project agent sessions and their workspaces. Session viewing and interaction follow the permissions you grant.
Set Read, Create, or Write & deploy access. Fine-tune permissions for agents, apps, gateways, automations, and services, then update or revoke access as your team changes.
Manage invitations and access in Settings → Users.
Understand the workspace, the tools, and the resource lifetimes before you get started.
Open Settings → Users to invite a teammate by email. Share one project, or choose global access to account-owned projects and sessions, including future projects. Set Read, Create, or Write & deploy access and refine it for agents, apps, gateways, automations, and services. Owners can update or revoke collaborator access.
Choose a supported app event, add any repository or event filters, then select an agent and write its prompt. You can add ordered agent steps; each receives the original event and the preceding result. Run history records progress, and enabled notification destinations receive started, finished, or failed updates. Configure the provider webhook to deliver the selected events.
These integrations currently support automatic resource discovery, webhook setup, and incoming event inspection in Apps. Agent automation triggers currently support mapped Git repository events. Product management event-to-agent workflows are not enabled yet.
Both. A session brings chat, files, an editor, terminals, Git controls, and running app previews into the same workspace. You can inspect changes, edit code yourself, and explicitly commit and push.
Mate and Codex agents support MCP integrations and managed skills. Configure tool approval policies, import a public GitHub skill or write manual instructions, and enable the skills you need. Each session retains its selected skill versions.
The workspace runtime and its published routes are cleaned up. Saved snapshots support resuming the session. Session-bound project services created by the agent suspend; regular services keep running. Retained data and snapshots follow their own storage lifecycle.
A merge or close event triggers cleanup of the PR’s preview workloads, builders, image repository, configuration, copied secrets, and dedicated disk. Retry handling and periodic provider checks catch failed cleanup and missed webhooks. Shared project resources remain separate.
No. AI Gateway supports configured provider routes and custom base URLs through an OpenAI-compatible API. Route credentials, client keys, token budgets, and routing settings belong to your gateway. Model availability depends on the configured upstream provider and your account access.
Connect GitHub, GitLab, or Bitbucket through a provider integration, or use SSH credentials. A Codebase lets you work with a repository and agent sessions without provisioning an application workload.
Connect a repository, choose an agent, and bring the rest of your stack along.