BusinessInsight System Architecture
BusinessInsight connects existing business data to mobile dashboards through a hosted control plane, a routing API, and a lightweight local Agent that keeps customer databases private.
Core Components
Admin Console
User authentication, tenant management, dashboard authoring, widget configuration, role views, and agent heartbeat visibility.
Hosted API
Central routing for authentication, metric requests, dashboard schemas, widget previews, client API fetching, and the Agent communication path.
Local Agent
A lightweight Windows process runs near the customer database and initiates outbound communication, avoiding public database exposure.
Technical Compatibility for IT Partners
The engine is database-aware but not tied to one vendor. It can work with many data architectures when credentials, connectivity, and query permissions are approved.
- Relational databases: SQL Server, Oracle, MySQL, PostgreSQL, MariaDB, and compatible ODBC sources.
- Legacy systems: Microsoft Access, FoxPro, FileMaker, local DBF files, and CSV-based operational exports.
- Proprietary ERPs: Custom local software databases where an approved query or endpoint can expose the required business metric.
- API sources: Client REST endpoints that return dashboard-ready JSON for approved widgets.
Security Model
Outbound-only Agent
The local Agent initiates communication to the hosted service. The customer database does not need a public IP address or inbound firewall rule.
Role-based dashboards
Each user sees widgets assigned to their company, role, and dashboard permissions rather than unrestricted database access.
Low-privilege connections
Reporting widgets should begin with read-only accounts or views. Writeback workflows should be explicitly reviewed and narrowly scoped.
Controlled expansion
Start with one proof dashboard, compare values against trusted reports, then expand into alerts and two-way workflows only after validation.