Português
EspañolFeatures
What is included — all of it, on every plan.
No module is contracted separately. What changes between plans is how many executors you get and the level of support.
The most common pain
Knowing what happened
History
Execution step by step, the full log, rows and bytes processed, and which version ran.
Dashboards
Home, Operations Centre and Analytics — 42 widgets, updated live.
Notifications
Email on two levels (process and step) plus an in-app notification bell.
Continuity
Not stopping when something falls over
Distributed executors
Several executors on the same database, with per-executor concurrency and per-process affinity.
Recovery after a crash
A run interrupted by an executor crash is closed out and restarted when it comes back.
Platform health
CPU, memory, disk, queue and database size, per executor.
Governance
Controlling who does what
Profiles and permissions
5 user profiles, per-process assignments, restricted tags and hidden mode.
Version control
What runs in production is the published version, not the working copy. Editing requires a check-out — administrators included — and every publication becomes a point you can roll back to.
Change approval
Whoever operates requests the change on screen; whoever builds responds. Approval is always human, and the whole exchange is recorded.
Recycle bin
Reversible deletion with configurable retention and automatic purging.
Without writing code
Ready out of the box
DataSync — data copy between databases
Source, target and field mapping on screen, across databases from different vendors. Four strategies: full load, date window, incremental by key and upsert. SQL scripts before and after, on both the source and the destination, and files as source or target — CSV, Parquet and Excel, with compression.
Database backup
Scheduled, compressed, with its own retention and an alert when it fails — for SQL Server, PostgreSQL, MySQL/MariaDB and Firebird. It is a logical backup (via the dump tool), not point-in-time.
Built-in variables
Today’s date, yesterday’s, the month’s — already formatted for each database’s dialect. Nobody writes date logic again.
Building
Assembling and maintaining the routines
Processes and steps
Sequence, failure condition, dependency, chaining and looping over data.
Scheduling
Reusable schedules, a time zone per schedule, recurrence by interval and at a fixed time.
Export / import
Processes and commands travel between installations as a versioned package.
Multi-language
Interface in Portuguese, English and Spanish, per user.
Databases
Seven to execute on, five to install on.
The platform keeps its own metadata in one database, and executes commands against another, larger set.
Execute commands on
Oracle · SQL Server · PostgreSQL · MySQL/MariaDB · Firebird · DB2 · ODBC
7 providers — this is where single-ecosystem tools tend to be weakest.
Install the platform on
Oracle · SQL Server · PostgreSQL · MySQL/MariaDB · Firebird
5 providers — you use the database your team already knows how to maintain.
Integration through the API
Supports integration through the API for running jobs and checking status: your system triggers the routine and follows the result, with nobody opening the screen. And the integration obeys the same rules as the screen — the user’s role, the daily quota and restricted mode all still apply, with no back door. Every access has an owner, an issuer, an expiry date, a scope limited to the authorised Jobs and a record of its last use, and can be revoked at any time. What is on the roadmap is labelled roadmap — we do not promise the future as the present here.