The answers your IT team will want first
Unbrick was designed around one rule: your plant’s data stays in your deployment. Everything below follows from it.
Read-only
Unbrick reads a nightly copy of your ERP’s reports. Nothing is ever written back to the ERP.
Outbound only
The connector at your plant pushes out over HTTPS with a key for your plant. No VPN, no inbound firewall rule, no database credentials leave the building.
One deployment per customer
Hosted or on your server, each plant has its own deployment and its own database. Nothing is shared between customers.
No third-party AI or analytics
No third-party AI, speech, analytics or telemetry service sees your data. The optional assistant runs inside your deployment.
Named people, recorded changes
Everyone signs in with their own account and role: viewer, planner, approver, admin. Every change records who and when.
Bad data refused
Stale, partial or repeated loads are refused before anyone sees them. Yesterday’s run stays current.
Questions IT asks
Does Unbrick change our ERP?
No. It reads scheduled reports the ERP already produces, from a folder. It has no write access to the ERP and never asks for any.
Do you need a VPN or a firewall change?
No inbound access at all. The plant connector only opens outbound HTTPS connections to your Unbrick address, the same way a browser does.
Where is our data hosted?
Hosted by us, your plant gets its own deployment and database on our server. On-premises, it runs on your server and nothing leaves your network. You can move between the two with a backup and a restore.
Is our data used to train AI?
No. No third-party AI service sees it. The optional assistant runs inside your deployment and answers from your plan, citing its sources.
What happens if the nightly export is broken or late?
The connector stops a damaged export at your plant. Unbrick refuses stale or partial data, keeps the last good run, and shows on every screen that the data isn’t current.
Who can see what?
Each person has a role. Planners prepare customer answers, approvers sign them off, viewers read. Station tablets are enrolled one by one and see only their station.
Backups, and leaving?
Hosted plants are backed up nightly. If you leave, you get a full export of every decision and response, and we delete your deployment.
Single sign-on?
Today, named local accounts with roles. Sign-in through your identity provider is on the roadmap.
Want the details for your IT team?
We’ll walk them through the connector, the data it reads and how a load is checked.