Your own server
Projects, users, resources and production records sit on one Arkite server in your network: physical, virtual or in your private cloud.
Security and data
Your production data stays on your own infrastructure.
Arkite runs on your own server, on-premises or in your private cloud. Access is role-based, every change is logged, and AI features that need the internet are off by default.
Where does Arkite store data, and who owns it?
All project and production data is stored on your own Arkite server, on-premises or in your private cloud, and remains fully owned by you. Workstations connect to that server over your own network.
- Server on a physical machine, a virtual machine or a VM in your private cloud
- Users from Active Directory, with roles per group
- Append-only audit log, protected by a hash chain
Security controls
What protects your data.
Role-based access
Users are local Arkite users or Active Directory users, with access per group. Default roles include System Admin, User Manager, Editor and Approver, and custom roles can be added.
Audit log
Every change to projects and settings is recorded with user, timestamp, previous and new values, in append-only records protected by a hash chain.
Controlled releases
Projects have a Draft, Review or Production status with a full version history. With the approval workflow, only Approvers release to Production. Operators have read-only access.
Backups and updates
Databases are backed up automatically when changes occur, with configurable frequency, and a backup is created before each server upgrade. Updates are installed centrally.
Sensor streams and images
Viewing, recording and snapshots of sensor streams are limited to users with a dedicated role. Images are stored only when explicitly configured.
Architecture and network
How Arkite fits your network.
| Details | |
|---|---|
| Server | Windows Server 2012 or higher, or Windows 10 Enterprise LTSC 2019 or higher, on a physical server, virtual machine or private cloud VM |
| Communication | REST API over HTTPS (port 443), reachable by workstations, MES and ERP, over a reliable wired network |
| Databases | Log data in SQLite by default, or in your own MySQL, MS SQL Server, Oracle or MariaDB, with configurable retention |
| Updates | Installed on the server; workstations detect the version difference and offer to update |
| Remote support | Through VPN or TeamViewer, via your firewall |
AI and privacy
AI only when you switch it on.
The AI detection algorithms of Arkite VISION run locally on the workstation and need no internet connection.
AI job generation and translation are optional integrations with OpenAI or Anthropic, configured with your own key. They are disabled by default, and send text to the selected provider only when enabled.
- AI detections run locally, without internet
- Optional AI for engineering, off by default
- Your own key with the provider you select
- Arkite NV processes personal data in line with the GDPR
Questions from IT and security teams
Is Arkite a cloud service?
No. Arkite runs on your own server, on-premises or in your private cloud. Your project and production data stays in your network.
Do workstations need internet access?
No. Only the optional AI job generation and translation need an internet connection, and only when they are enabled.
How are users managed?
Centrally on the Arkite server, as local users or Active Directory users with access per group. A user can log in on every connected workstation.
Can changes to instructions be audited?
Yes. Every change to projects and settings is logged with user, timestamp and previous and new values, in append-only records protected by a hash chain.
How does Arkite handle operator privacy?
Access to sensor streams and recordings is limited to users with a dedicated role, and images are stored only when this is explicitly configured. Arkite NV processes personal data in line with the GDPR.
Questions about security or architecture?
Our team walks your IT department through server sizing, network requirements and data handling.