Self-hosted automation
Wire your tools together. Keep the wiring.
DEV3 Cogvane is a visual workflow builder you install on your own server. Draw a flow, publish it, and every run is kept with each step, input and error, ready to retry.
Runs on your server · Encrypted vault · Safe by default

37
node types
50
safe functions
0
code nodes
1
worker to keep running
01 / How a run works
Trigger, nodes, history.
One run is one trip down the cables. You can read every stop afterwards.
01
A trigger starts a run
A signed webhook, a hosted form, a schedule in the flow's time zone, a manual button or the REST API. Duplicates are dropped by idempotency key.
POST /hooks/k_7Qm2xA02
Nodes move items along cables
Each node receives items and passes items on. If, Switch, Loop and Merge route them; expressions reshape them. Branches run one after another, in order.
{{ $json.total | format(2) }}03
Every step is kept
Inputs, outputs, timings and errors are stored per step, with secrets redacted. Retry a failed run from the step that broke; finished steps are reused.
run r_91f3 · 7 steps · 412 ms02 / Expressions
A formula language, not a code box.
Edit the sample, change the expression, see the result. This is the same engine that runs on the server, with the same 50-function allow-list and the same limits.
Try the last preset: reaching for constructor is refused, not evaluated.
03 / Node catalogue
37 node types, no code node.
Connectors are generic on purpose: HTTP, webhooks, forms, schedules and email. Anything with an API is an HTTP node away.
Triggers4
- Webhook
- Schedule
- Manual
- Form
Actions6
- HTTP request
- Send email
- Respond to webhook
- Store data
- Wait
- Execute flow
Simulated apps (demo)5
- Sheet rows
- CRM contact
- Chat message
- Payment event
- Storage file
Transform17
- Set fields
- Rename keys
- Remove keys
- Filter list
- Map list
- Merge
- Split out
- Aggregate
- Sort
- Limit
- Remove duplicates
- Date format
- Text template
- JSON parse
- JSON stringify
- CSV parse
- CSV build
Logic5
- If
- Switch
- Loop over items
- Stop and error
- No-op
04 / Run history
Failures are a page you can read, then retry.
When a step fails, the run stops there and keeps everything it learned. Fix the cause, then retry from that step: finished steps are reused, not repeated.
Run r_91ee, step by step
- Webhook3 ms
- HTTP request2.2 s
- Ifnot reached
- Send emailnot reached
http_timeout
The server did not answer within 10 s.
Retry from HTTP request
Retries create a child run that links back to the original.
05 / Vault and network safety
Secrets stay sealed. Requests stay public.
A workflow tool is a machine that makes requests on your behalf. Cogvane assumes someone will try to point it at your internal network, and refuses.
Encrypted vault
- Credentials are sealed with AES-256-GCM using a key you hold (COGVANE_VAULT_KEY).
- Flows reference credentials by name; the value is never shown again, never exported.
- Run history redacts the full value, its head and tail, base64 and basic-auth forms.
- Viewers see run data with payloads hidden.
Blocked by default
Every address is checked after DNS resolution and pinned for the connection, on every redirect.
10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16Private networks127.0.0.0/8, ::1/128Loopback (this server)169.254.0.0/16, fe80::/10Link-local and cloud metadata (never allowable)100.64.0.0/10Carrier-grade NAT0.0.0.0/8, 224.0.0.0/4, 240.0.0.0/4Unspecified, multicast, reservedfc00::/7, ff00::/8, 2001:db8::/32IPv6 unique-local, multicast, documentation192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24Documentation rangeslocalhost, *.internal, *.local, *.lanInternal host names
Ports 80, 443, 8080 and 8443 only, unless a workspace rule adds more. The operator can allow private targets; metadata addresses can never be allowed.
06 / Templates
Start from a flow that already runs.
Every template is a real flow. Open it, change the URLs, publish.
Order to sheet
Receives an order webhook, works out the total, appends a row to a sheet and counts the day.
Webhook trigger > 4 nodes
Form to email
A hosted contact form that emails your team and creates a CRM contact.
Form trigger > 3 nodes
Daily digest
Collects the latest rows into one summary email every weekday.
Schedule trigger > 6 nodes
Big payment to chat
Reads a payment event and tells the team in chat when it is large.
Manual trigger > 5 nodes
CSV transform
Parses CSV text, computes line totals, sorts the rows and builds a new CSV.
Manual trigger > 5 nodes
Retry with backoff poller
Calls an unreliable API and retries with exponential backoff before giving up.
Manual trigger > 3 nodes
Webhook relay with HMAC
Accepts signed webhooks, forwards the payload to another service and answers with the result.
Webhook trigger > 4 nodes
Batch notifier
Loops over a list in batches, posts each batch to a service and then reports how many went out.
Manual trigger > 5 nodes
07 / Self-hosting
Two processes and a database.
No queue service, no cache, no cloud account. Unzip, configure, start the app, start the worker.
- Node 20.9+ for the app and the worker.
- MongoDB 6+, single node is fine, a replica set is better.
- A process manager (pm2 or systemd) so the worker stays up.
- A setup wizard checks your server and creates the first admin.
- Throughput is thousands of runs per hour per worker; add workers to add capacity.
08 / Plans
Plans for the hosted workspace model.
You set the caps. A self-hosted copy can run any number of workspaces, each on one of these plans.
Starter
For small teams and volunteers
$0/mo
- 5 active flows
- 2,000 runs / mo
- 20,000 operations / mo
- 7 days of run history
Team
PopularFor teams that automate daily
$29/mo
- 50 active flows
- 25,000 runs / mo
- 250,000 operations / mo
- 30 days of run history
- Schedules every 5 minutes
Business
For heavy workloads
$99/mo
- 250 active flows
- 150,000 runs / mo
- 1,500,000 operations / mo
- 90 days of run history
- Schedules every minute
09 / Honest answers
Limits, stated up front.
Which apps does it connect to?
Connectors are generic: an HTTP request node, webhook and form triggers, and an email node that writes to an outbox until you configure SMTP. There is no marketplace of third-party apps; you describe an API once as an HTTP node and reuse it. The demo includes five simulated app nodes that talk to a built-in mock host only.
Is the expression language JavaScript?
No. Expressions are a sandboxed formula language with a fixed list of 50 functions. There is no custom code node, no eval and no access to the server. That is what lets one workspace share a server with another safely.
Do I need to run anything besides the web app?
Yes. Runs execute in a separate Node worker (npm run worker) that you keep alive with pm2 or systemd, next to MongoDB 6 or newer. Without the worker, flows can be edited and test-run but queued runs, schedules and waits will not progress.
What happens if the worker crashes mid-run?
The run is reclaimed by the next worker. Execution is at-least-once per node after a crash, so make side effects idempotent (the HTTP node can send an idempotency key).
Can a flow call a service on my private network?
Not by default. Private ranges, loopback and cloud metadata addresses are blocked. The operator can switch on private targets and a workspace owner can add allow-list rules; metadata addresses can never be allowed.
Is it a high-throughput event bus?
No. It is sized for thousands of runs per hour per worker, with caps on node executions, loop sizes, payload size and run time. Caps can be lowered but not raised beyond the hard limits.
Where are credentials kept?
In an AES-256-GCM encrypted vault inside your own database. Back up the vault key: without it stored credentials cannot be recovered.
See the wiring.
Sign in to the demo with one click and open a flow that has run, failed and been retried.