Persistent flows
Saved graphs and custom components survive restarts and releases.
Design, test, and deploy agent flows using reusable drag-and-drop components and Python-based integrations. Darwa adds the managed runtime, HTTPS, persistent storage, and lifecycle tracking around it.
Langflow keeps the visual graph and the code honest with each other. Every component is a Python class you can read, fork, or replace, which makes it the fastest way to test an idea you intend to hand to engineers.
The visible capabilities come from the verified catalog entry; secrets and signed installer assets remain private to the backend.
Saved graphs and custom components survive restarts and releases.
The first admin credential is generated per deployment rather than left at a published default.
A working address with a valid certificate from the first health check, no manual TLS setup.
The deployment is only marked live once the application answers a real health probe.
Typed building blocks for models, memory, and tools that snap together on a canvas.
Components are real Python classes you can read, fork, or replace.
A selection of what the upstream project supports. Credentials for any third-party service are yours to add and revoke.
Each saved flow becomes a callable endpoint, so the graph you tested in the editor is the same one your application invokes.
Assemble and test prompts, models, memory, tools, and retrieval before integrating an application.
Connect document processing, vector search, model calls, and answer generation visually.
Turn an approved graph into an API-backed workflow that a product can call.
The hosting layer is the same for every agent, which is what makes a one-click install honest.
Deployments run from a reviewed catalog entry rather than an arbitrary image you have to trust.
Each agent gets its own workload boundary, not a shared container with an unrelated website.
Plan storage is allocated up front so application state survives restarts and releases.
A working address with a certificate from the first health check, with custom domains where supported.
Runtime and resource signals come from the actual workload, so a failure is visible rather than silent.
Grace, suspension, retention, and restoration follow the plan instead of an untracked server.
One AI Agent subscription covers the managed runtime, storage, and endpoint. Model provider usage is billed by that provider.
Live pricing is temporarily unavailable. Langflow needs at least 1 vCPU, 4 GB RAM, and 10 GB of storage.
View AI agent plansDarwa keeps Langflow selected when the authenticated launch flow opens.
Use an active agent subscription or choose a plan with enough compute and storage.
Start with an agents.darwa.co address or select an eligible verified custom domain.
The backend verifies the manifest, creates the runtime, and records its service and container identities.
Darwa hosts the open-source application independently; upstream licensing and product behavior remain with its project.
Yes. Custom components are Python classes, and code you add is stored on the deployment's persistent volume so it survives restarts.
Yes. Published flows expose an API endpoint over the managed HTTPS address, authenticated with a key you generate in the interface.
Memory components persist to the deployment's storage. Which conversations are retained, and for how long, is determined by the components you place in the graph.
Use Langflow when the hard part is the AI graph itself, and n8n when the hard part is connecting many business systems around it. They are frequently deployed side by side.
Darwa manages the verified deployment manifest, isolated runtime, persistent storage allocation, HTTPS endpoint, health tracking, usage visibility, and paid-plan lifecycle. You manage the agent's models, credentials, tools, content, and decisions.
Choose Install Langflow, sign in, and select an AI Agent plan if the workspace does not already have one. The launch flow keeps Langflow selected while you choose its address and start the managed deployment.
The current catalog minimum is 1 vCPU, 4 GB RAM, and 10 GB of storage. Real requirements depend on concurrency, models, document volume, integrations, and enabled features.
Darwa allocates persistent storage according to the selected plan. Important application data should still follow the backup and recovery practices required by your business.
The application can start with a managed Darwa address. A domain you own can be selected when custom-domain support is available for the launch flow and its DNS is verified.
No affiliation is implied. Langflow is a third-party open-source project. Darwa provides independent managed hosting and links to the upstream repository for project information and licensing.
Sign in, pick a plan with enough resources, and Darwa builds the managed runtime around it.