Schedule
Cron-based schedules run a process at a set time or interval, without anyone lifting a finger.
How Automize is built – a cloud control plane, distributed execution, and an audited, tenant-isolated data model. Written for architects and technical evaluators.
Automize separates the control plane – the cloud application that designs, schedules, and governs automation – from the data plane, where bots run the work inside your own environment. Bots dial outbound only: they poll the control plane for commands and stream results back, so there are no inbound ports to open on your network.
See the Trust Center for hosting, data residency & sub-processors
Every automation follows the same governed path from design to a tamper-evident record. Failures do not restart from zero – typed retries and resume-from-step pick up where the run left off.
Automation is event-driven. The same process can be started by any of these, alone or in combination.
Cron-based schedules run a process at a set time or interval, without anyone lifting a finger.
An external system starts a run by calling a per-process URL – tokenised and optionally HMAC-signed to prove integrity.
Start, queue, and resume runs programmatically – post to a process to run it on demand from your own systems.
Platform events fire a run in response to what happens elsewhere in your workspace, with priority ordering.
Operators start attended or unattended runs directly from the app whenever they need to.
The same process definition can run in whichever place fits the work – no rewrite required.
A person triggers the bot on their own desktop – ideal for human-in-the-loop steps, approvals, and tasks that need judgement alongside automation.
Bots run on servers to a schedule or trigger, with no operator present. Pools distribute work across bots and apply back-pressure when demand spikes.
API-to-API integrations run entirely in the control plane – no bot, no desktop. Fan-out, join, and mapping steps orchestrate data between systems directly.
The control plane is fully managed for you. Execution happens wherever your systems and policies require.
The control plane runs as a managed service – nothing for you to provision, patch, or scale. There is no infrastructure to stand up before you begin.
Bots run on your own desktops and servers, reaching internal systems locally. They connect out over HTTPS on a strict egress allow-list – no inbound ports, no wildcard outbound.
Where regulation or policy requires it, the web portal can be deployed on-premises as a scoped engagement, sized to your environment.
Automize connects to systems through their APIs wherever one exists, with a shared authentication layer that speaks the common enterprise protocols. UI automation is the fallback – used only when there is no API – and it is hardened with self-healing selectors that adapt when a screen changes.
When the built-in library does not cover something, your team can extend the platform without waiting on ours.
A documented REST API (OpenAPI 3.1) covers runs, processes, and credentials, with a live collection you can import and try.
Add custom actions and connectors in Python – subclass a plugin base, declare a JSON schema, and the designer renders the inputs automatically.
A large built-in catalogue, plus a generic HTTP connector for any REST or SOAP endpoint with per-tenant host and header configuration.
Install ready-made process templates from the marketplace and adapt them to your own workflow.
AI speeds up building and running automation while you stay in control. It is powered by OpenAI and Anthropic, with your choice of provider and model per workspace.
Conversational assistants help you build processes, answer product questions, and work alongside your wikis.
Vision-capable models read invoices, forms, and other documents and images, extracting structured data your automation can act on.
AI suggests field mappings and groupings, renames steps, diagnoses failures, and drafts flows – every suggestion is yours to accept or reject.
Choose OpenAI or Anthropic per workspace, and pick the model per task. No single provider is locked in.
Credentials are never written into an automation. They are held in an encrypted vault and resolved by reference only at the moment a bot needs them.
Credentials are encrypted at rest. Names and usernames are browsable for reuse; the secret itself is never displayed in the interface.
Store secrets in the platform vault, AWS Secrets Manager, or the bot host operating-system keychain. The database only ever holds a reference.
Automations reference a credential by identity. A scanner flags any hardcoded secret, so plaintext cannot creep into a definition.
Per-credential grants (metadata-only, use-at-runtime, or edit), rotation and expiry policies, and a hash-chained access log.
A request crosses three layers before it can touch data. Each layer is independent – a gap in one is caught by the next.
Full security controls, compliance & frameworks in the Trust Center
Automation that behaves predictably under load and recovers cleanly when something breaks.
Work is distributed across bots through pools, with back-pressure so a demand spike queues rather than overwhelms.
Failures are classified, so a transient network blip retries automatically while a genuine business error surfaces for a human.
A run that fails part-way does not start over – it resumes from the step it reached, so no completed work is repeated.
Runs and pools report against service-level targets, so a stalled queue is visible before it becomes a missed deadline.
The controls that keep automation auditable and deployments safe as the platform evolves.
Sensitive operations are hash-chained end to end. The record is append-only and verifiable – you can prove what happened and when.
Schema changes and feature flags move through continuous integration with automated checks before anything reaches production.
Runs, queues, and integrations emit structured logs and metrics, so operators can trace a single run from trigger to result.
The controls a security or compliance reviewer looks for. The full detail – hosting, sub-processors, and frameworks – lives in the Trust Center.
Customer data is hosted in the European Union. Egress to other regions is denied at the network layer, not just by policy.
TLS in transit and encryption at rest across the database, file storage, and backups – no plain-text tier.
Sensitive actions are chained with HMAC-SHA-256 and verified nightly. Audit exports are written to write-once (WORM) storage.
A tenant-erasure process removes customer data on offboarding, while preserving legally required audit records under lock.
Logs are scrubbed of personal data and secrets before they are written to disk or sent to error tracking.
Automated, encrypted backups guard against data loss, retained on a defined schedule.
Hosting, sub-processors & compliance frameworks in the Trust Center
Bring your architecture and security teams. We are happy to walk through the topology, the security model, and how Automize fits your environment.