English
Automatisch Hosting
Connect services and automate repetitive work through configurable integration workflows.
No setup fees-
One click deploy -
4 GB RAM Memory needed -
50 GB Disk Space Needed -
From 10 € Price
Official links
Automatisch’s official links and original website
Automatisch Website
More
Tech
- Docker image
- automatischio/automatisch:latest
- Default port
- 3000
- Database
- postgres
How Automatisch works
Automatisch builds workflows from a trigger followed by one or more actions. A trigger may react to a new record, schedule, or incoming webhook, then actions pass selected data to other connected applications. Users author the workflow in the browser, while background workers execute jobs and Redis coordinates queued activity alongside PostgreSQL.
Connections store credentials for external services so a workflow can call their APIs without asking for a password during every run. The application encrypts saved connection secrets using configured keys. That protects stored values at rest within the application design, but teams still need to limit who can create workflows, rotate external tokens, and remove connections that are no longer required.
Key Automatisch features
Visual trigger-and-action design makes straightforward automations understandable to people who do not want to write a complete integration service. Webhooks handle real-time inbound events, while scheduled triggers support recurring jobs. Execution history helps investigate failures and understand which step received or produced unexpected data.
Integration coverage depends on the connectors present in the installed release. A provider can also change its API, permissions, or rate limits independently. Test each business-critical workflow with representative data, define ownership for credentials, and keep a manual fallback for processes that cannot pause when an external connection fails.
Automatisch vs Zapier
Automatisch is a self-hosted automation engine that runs workflows, workers, queues, and connection data on infrastructure controlled by the operator. Zapier is a provider-managed automation platform with thousands of app connections, workflow templates, webhooks, and a surrounding cloud service that removes server maintenance.
Zapier may suit teams that need its broad connector catalogue and prefer the provider to operate execution infrastructure. Automatisch is more appropriate when supported integrations are sufficient and workflow data should remain on a self-hosted stack, while accepting responsibility for connector compatibility and operational monitoring.
Who uses Automatisch
Operations teams move records between approved services, sales groups synchronise routine updates, and developers expose simple webhook-driven processes without building a dedicated worker for every task. Small organisations use it to reduce repetitive copying between tools that already have compatible APIs.
The application is not a substitute for testing or process design. A workflow can duplicate, omit, or transform data incorrectly if trigger conditions and field mappings are wrong. Use test accounts where possible, inspect early executions, and avoid granting a connection broader permissions than the automation actually needs.
Self-hosting Automatisch: requirements and cost
Workload depends on active workflows, trigger frequency, action count, payload size, connector latency, retries, execution history, and concurrent workers. PostgreSQL stores users, workflows, encrypted connections, and execution records; Redis and a worker support queued processing. PostgreSQL is included but unmanaged, with its memory outside the exported application minimum.
AvaHost maps Automatisch to Plan 4 at €20. One-click deployment, a custom webhook domain, automated HTTPS, automatic application updates, and scheduled backups are included. Application email is disabled, so password-recovery and other mail-dependent functions are unavailable; triggers, actions, webhooks, workers, and compatible external integrations remain separate capabilities.
F.A.Q
Automatisch starts at €20 on Plan 4 after accounting for PostgreSQL, Redis, a worker, and the web application. Active workflows, trigger frequency, action count, payload size, retries, execution history, connector latency, and concurrency influence consumption. Test the real integration pattern because two workflows with the same step count can produce very different loads.
The one-click deployment provisions PostgreSQL and connects Automatisch automatically. Users, workflows, encrypted connection records, execution data, and settings depend on it. PostgreSQL is included but unmanaged, while Redis and the worker are separate packaged services. Administrators should plan updates and recovery across the database, encryption keys, queue services, and persistent application data together.
A custom domain can be assigned to the Automatisch interface and webhook endpoints, with automated HTTPS enabled after DNS resolves. Use the final address when registering callbacks in external services. A later hostname change requires updating every provider that posts to the old URL and testing signatures, secrets, redirects, and workflow execution again.
AvaHost disables application email, so password-recovery and any other mail-dependent Automatisch functions are unavailable. Workflow triggers, actions, webhooks, workers, and compatible API integrations continue independently of email. Owners should retain administrator credentials securely, document an access-recovery process, and avoid designing an automation that expects the hosted application itself to send mail.