AI-native deploys

Ship from your IDE. Without DevOps overhead.

Streamline CI/CD and deploy directly from code. Wire dFlow MCP in your AI editor and land on the servers you already pay for.

layout.tsx
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
import type { Metadata } from 'next'
import { Geist, Geist_Mono } from 'next/font/google'
import { ThemeProvider } from '@/providers/theme'
import { QueryProvider } from '@/providers/query'
import { Toaster } from '@/components/ui/sonner'
import './globals.css'
const geist = Geist({ subsets: ['latin'] })
const mono = Geist_Mono({ subsets: ['latin'] })
export const metadata: Metadata = {
title: 'dFlow',
description: 'Ship from your IDE.',
}
export default function RootLayout({ children }) {
return (
<html lang='en'>
<body>
<ThemeProvider>{children}</ThemeProvider>
</body>
</html>
)
}

deploy my ecommerce site on AWS EC2 using dflow MCPdflow MCP

Your cloud. Your stack. Your editor.

dFlow sits between the infrastructure you already pay for and the apps you ship — drive deploys from the dashboard, git, or your AI editor through MCP.

Your cloud

AWS
GCP
Azure
Hetzner
DigitalOcean

+ bare metal · VPS · on-prem

Your stack

Postgres
MySQL
n8n
WordPress
Redis

+ any Docker image · 100+ templates

MCP

Driven by your AI

AntigravityAntigravity
CursorCursor
Claude CodeClaude Code
CodexCodex
GitHub CopilotGithub Copilot

Editor deploy

3 steps from editor to live URL

Deploy from the AI editor you already use onto the servers you already pay for.

1. Connect the dFlow MCP

{
  "mcpServers": {
    "dflow": {
      "url": "https://app.dflow.sh/api/mcp"
    }
  }
}

Add the dFlow MCP in Cursor, Claude, Codex, or any MCP-compatible editor. One config and your agent gets the full dFlow toolset in chat: apps, services, envs, and deploys.

2. Publish repo as template

convert my blog website into a dFlow template by attaching a MongoDB database using dflow mcp

Ask the agent to convert the working tree into a dFlow template, dFlow infers your stack, services, and dependencies and outputs a reproducible template no hand-written YAML.

3. Deploy from the editor

BUILDING
# 69a55931be
Triggered a minute ago…
SUCCESS
# 69a55911be
Triggered 2 days ago

Tell the agent where to run: Hetzner, EC2, a managed worker, and more. dFlow provisions, builds, and rolls out; you get live deploy logs in chat the moment it goes live.

Agent toolkit

Your agent gets the full deploy surface in chat

No shell scripts to memorize. dFlow MCP exposes the same operations you would run in the dashboard as tools your editor can call.

Create services

Spin up apps, wire git repos, and map domains without leaving the thread.

Manage env vars

Add, update, and sync secrets across preview and production environments.

Attach databases

Provision Postgres, MySQL, MongoDB, or Redis beside your app on your worker node.

Trigger deploys

Kick off builds, watch rollout status, and get preview URLs back in chat.

Stream logs

Pull deployment and runtime logs into the editor when something breaks in prod.

Publish templates

Ask the agent to convert a working repo into a reusable dFlow template.

The new DevOps loop

Production breaks? Your AI already has the logs.

When a deployed service crashes, stream deployment logs straight into your editor, resolve with your favorite AI tools, apply the fix, and push back to production without leaving your workflow.

  • Logs streamed to your editor
  • Diff-friendly fixes you can review
  • Ship the patch back to prod in one flow
web · 5xx rate +320%
IDE chatdiff
await client.query(sql)
await client.query(sql, [id])
Apply

Deployment timeline

Fix mergedBuildingDeployed (47s)

FAQ

AI workflow questions

Common questions about MCP setup, supported editors, and shipping from chat.

Can't find what you're looking for? Contact our customer support team

Wire your editor and ship

Add the dFlow MCP, connect a worker node, and ask your agent to deploy. You keep the cloud bill and the control plane.

AI workflow | dFlow