No one exports spreadsheets anymore.
A small program runs on your own server, next to your ERP or DMS. Every few minutes it reads what changed — read-only — and ships it over a channel encrypted and authenticated on both ends.
Works with the system you already have — ERP, DMS or spreadsheet. Nothing changes in your operation, and no port is opened on your network.
Decision-maker: the security guarantees · IT: the full install
It reads. It never writes.
The agent is deliberately small and constrained. What it can do fits in three lines — and so does what it can’t.
Reads only data that changed — sales, installments, records with recent history.
Ships to AutoController over a channel encrypted and authenticated on both sides (mTLS).
Runs on its own as a system task: starts with the machine, recovers from crashes, keeps logs.
Writes nothing to your system — database access is read-only.
Opens no inbound port on your network: the agent calls out to the cloud, never the other way — and always to a single destination your IT can pin in the firewall.
Sends data nowhere but AutoController — and never talks to the cloud database directly, only to the API.
Seven layers between your database and the internet.
The same end-to-end model: certificate identity, an mTLS channel and least privilege at every link.
One certificate per agent identity
Each agent gets its own digital certificate, valid for 90 days and renewed automatically. Without it, the API refuses the connection.
mTLS on both ends channel
All traffic is encrypted and mutually authenticated: the agent proves who it is — and so does the server.
A single destination, allowlisted destination
The agent talks to one fixed address — api.autocontroller.ai. Your IT can restrict the server’s outbound traffic to that destination in the firewall, and the agent only trusts AutoController’s CA: diverted traffic never authenticates.
Encrypted at the source credentials
Your system’s user and password stay encrypted (AES-256-GCM) on the machine itself, with the key in the Windows credential vault. No one types or sees it.
One tenant per company isolation
In the central database each company sees only its own data — isolation enforced by the database, not the application.
Read, and read only privilege
The agent’s database user is read-only. The full-access credential never leaves AutoController’s servers.
Immediate cut-off revocation
A compromised certificate is revoked instantly, server-side — the agent loses access on the next cycle.
Installed in minutes.
A local wizard walks through four steps — on the machine your system already runs on, no third-party software.
1 · Database
Read-only credential for your ERP or DMS. Everything stays on this machine, encrypted in the Windows credential vault — encryption details live in the "Encrypted at the source" layer; no one types or sees it.
Installation guided by the AutoController team, together with your IT. Interactive demo of the local wizard — data shown is sample data.
Incremental, idempotent, failure-proof.
Reads only what changed. Change detection by history date, re-scanning 5 minutes back — late postings don’t slip through.
Reprocessing is cheap. Every row carries a content hash: unchanged rows are skipped, changed ones replace the previous version.
The checkpoint only advances on success. Failed? The watermark stays put and the next cycle reprocesses the same window. Nothing is lost midway.
Ship raw, normalize on arrival. The agent doesn’t transform data: the API normalizes, validates and preserves the original payload for audit.
Every run, on the record.
Cycle by cycle: when it ran, how many rows, how long, and where the checkpoint stopped. The history shows up in the panel — no SSH, no asking IT for logs.
- Run status and history right in the panel.
- A failure never advances the checkpoint — the next cycle reprocesses the same window.
- The certificate renews itself before expiring.