API client
Reproduce REST or GraphQL requests, save variables, inspect responses, and attach failures to AI.
IDE for microservices development
IDE for microservices development: Manage services in one workspace.
Run separate repositories, containers, databases, API requests, browser sessions, tests, and coding agents without flattening the architecture into one project.
The stack stays connected while repositories stay independentProject, branch, package, change, and runtime state remain visible across services.
The problem
A local microservices stack is a coordination problem, not a folder problem.
One feature request can cross an edge service, API, event consumer, database, shared package, and frontend. Each process has its own command, environment, port, logs, tests, and repository state.
When these live in separate IDE windows and terminal tabs, developers spend time locating the right process and reconstructing request flow instead of debugging it.
How Flame solves it
Operate the stack from setup through cross-service verification.
- 01
Group the service repositories
Add the frontend, APIs, workers, shared packages, and infrastructure projects without changing their Git boundaries.
- 02
Define how the stack starts
Create a group run configuration with each service command, Docker Compose action, working directory, environment, browser URL, or health request.
- 03
Observe every runtime
Keep service terminals, container logs, CPU and memory state, browser output, and test watchers attached to the correct project.
- 04
Trace across boundaries
Search files and symbols across repositories, reproduce the request in the API client, and inspect the database state behind the response.
- 05
Delegate isolated changes
Run agents in service-specific projects or worktrees, review each diff, and merge only after the full stack passes verification.
Docker and Compose
See which service is unhealthy before reading every log.
Use the Containers panel to inspect Docker and Docker Compose workloads, follow logs, check CPU and memory activity, open a shell, and control container lifecycle without leaving the workspace.
Keep the container action beside the repository and terminal that define it. That makes it easier to distinguish an application failure from a stale image, missing environment value, or failed dependency.
Container state in the development workspaceInspect, restart, stop, remove, or open a shell from one panel.
Cross-service evidence
Follow one failing request through every layer.
Database workspace
Inspect schemas and data, run native queries, and connect the result to the responsible service code.
Cross-project search
Find route names, event types, configuration keys, and shared symbols across every repository.
Browser context
Capture the rendered page, DOM, console errors, failed loads, and screenshots for frontend failures.
Tests and profiling
Run service-specific test suites and inspect performance where the failing code executes.
Parallel agents
Assign independent service changes to separate projects or worktrees and keep every result reviewable.
Product walkthrough
Watch Flame configure and run a real project workflow.
Official Flame demo
Let AI Configure and Run Any Project in 1 Click
See how Flame turns project-specific commands, working directories, environment values, URLs, and checks into a repeatable launch configuration.
FAQ
Microservices development questions
Run the architecture as one development system.
Download Flame to manage service repositories, runtimes, data, requests, and agents in one workspace.
Free to use on macOS, Windows, and Linux.