Persistent workflows
Workflows and execution history are written to plan storage, so a restart loses nothing.
Build visual automations across applications, APIs, databases, and AI models with hundreds of integrations. Darwa adds the managed runtime, HTTPS, persistent storage, and lifecycle tracking around it.
n8n is the automation layer teams reach for when a workflow has to touch six systems and still be readable by the person who did not build it. Drag nodes, branch on conditions, and drop to code only where you actually need it.
The visible capabilities come from the verified catalog entry; secrets and signed installer assets remain private to the backend.
Workflows and execution history are written to plan storage, so a restart loses nothing.
Stored credentials are encrypted with a key created for this instance alone.
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.
Public webhook URLs and cron triggers work the moment the endpoint is live.
Hundreds of prebuilt integrations, plus HTTP and code nodes for anything unlisted.
A selection of what the upstream project supports. Credentials for any third-party service are yours to add and revoke.
A trigger wakes the workflow, nodes run in order against your credentials, and the execution history is written to persistent storage.
Connect forms, CRM records, email, payments, support tools, and internal APIs.
Combine models, retrieval, business rules, approvals, and downstream actions in one visual flow.
Run recurring reports, synchronization, cleanup, and notification jobs without a developer laptop.
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. n8n needs at least 0.5 vCPUs, 1 GB RAM, and 5 GB of storage.
View AI agent plansDarwa keeps n8n 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.
Concurrency depends on the plan's CPU and memory rather than a workflow count. Long-running or memory-heavy nodes reduce how many can overlap, so size the plan to the busiest expected moment.
Yes. The managed HTTPS endpoint is live as soon as the deployment passes its health check, so production webhook URLs resolve without extra tunnelling or port configuration.
Yes. n8n workflow JSON exported from another instance can be imported once you sign in. Credentials are not included in exports and must be re-entered.
Completed executions stay in persistent storage. An execution in flight at the moment of a restart does not resume automatically, so design critical workflows to be safe to retry.
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 n8n, sign in, and select an AI Agent plan if the workspace does not already have one. The launch flow keeps n8n selected while you choose its address and start the managed deployment.
The current catalog minimum is 0.5 vCPUs, 1 GB RAM, and 5 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. n8n 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.