Arkite
EN
Book a demo
Operator guidance for IT and digital manufacturing

The operator layer for your MES. Connected, central and secure.

Arkite runs as a server-client platform inside your own infrastructure. One central server holds projects, users and production records, and connects the manual workstation to the MES, ERP, PLC and BI systems you already run.

Book a demoView integrations
Sound familiar?

What IT and digital manufacturing teams tell us.

  • The shop floor already runs too many isolated tools.

    System landscape

  • Every new system on the floor becomes another integration project.

    Integration effort

  • Production data cannot leave our infrastructure.

    Data ownership and security

  • Every workstation is another device to configure, update and support.

    Maintainability

How Arkite solves it

Four IT questions, and how Arkite answers them.

  1. Arkite architecture: the Arkite server with projects and log databases in the server room or cloud, connected over the network to the Arkite PCs, projectors and workstation tools on the factory floor, with VPN remote support through the firewall
    01

    One central server instead of tools per station.

    Today
    Separate tools at every station become shadow IT that nobody can maintain.
    With Arkite
    All projects, users and production data sit on one Arkite server: physical, virtual or in your private cloud. Workstations and editors connect to it.
  2. Complete Arkite workstation with projector, 3D sensor, operator screen, smart tool, bins and scanner
    02

    Connect systems without writing code.

    Today
    Linking the manual station to MES, PLC and tools usually means custom code.
    With Arkite
    Arkite runs stand-alone or connected. OPC UA, MQTT, S7, Modbus, HTTP, Open Protocol, databases, scanners and printers are set up through configuration, and a REST API is available.
  3. Arkite Editor connected to the central Arkite server, which supplies every workstation on the production line
    03

    Your data stays on your own infrastructure.

    Today
    New shop floor systems must meet your security and data policies.
    With Arkite
    Data stays on your server. Users come from Active Directory, every change is logged and cannot be altered, and AI features are off by default.
  4. A plant with kitting, assembly, packaging and a control room, all connected to Arkite
    04

    Add workstations without rebuilding anything.

    Today
    A pilot that works on one station often has to be rebuilt for the next line.
    With Arkite
    New workstations connect to the existing server and immediately have the existing projects. The same setup carries one station, a line or several plants.
What changes for you

One maintainable platform instead of isolated tools.

  • Down

    Integration effort

    Configured modules instead of custom interfaces.

  • Down

    Isolated shop floor tools

    One platform for guidance, validation and inspection.

  • Down

    Maintenance per station

    Projects, users and updates managed centrally.

  • Up

    Data ownership

    Data stays on your server, in your network.

  • Up

    Data availability

    Structured execution data for MES and BI.

  • Up

    Scalability

    From one workstation to multiple plants.

Detailed requirements are listed below and reviewed with our technical team.

Optional MES integration

When you connect an MES: how jobs reach the workstation.

  1. 01

    The job is created

    Jobs are created in Arkite, or created in the MES and sent to the Arkite server through the REST API.

  2. 02

    Engineering prepares

    Process engineers adapt the job to the physical workstation and release it to the correct stations.

  3. 03

    Workstation retrieves

    When an operator logs in, the workstation retrieves the correct job and product variant automatically.

  4. 04

    Data returns

    Execution data is logged centrally and available to MES, ERP and BI through the database, CSV export or the API.

Infrastructure

Server and network requirements.

  • Windows Server 2012 or higher, or Windows 10 Enterprise LTSC 2019 or higher
  • 8 GB RAM up to 10 workstations, 16 GB above 10
  • 100 GB SSD after OS installation, plus 20 GB per workstation
  • Wired network connection between workstations and server
  • REST API over HTTPS (port 443) reachable by workstations, MES and ERP
  • Automatic database backups when changes occur, configurable
  • Server updates distributed to workstations on version mismatch
  • Automatic backup before each server upgrade

Questions from IT

Does the workstation depend on an external AI service?

No. AI job generation and translation are used by engineers in the Arkite software. The AI detection algorithms of Arkite VISION run locally on the workstation and need no internet connection.

Which AI providers are supported, and what data is sent?

AI job generation and translation use an integration with OpenAI or Anthropic, configured with your own key. These integrations are optional, disabled by default and require an internet connection. Text is only sent to the selected provider when the integration is enabled. Project and production data stay on your own Arkite server.

Where is the API documented?

The REST API is documented on SwaggerHub, and an API tester is available in the Arkite software.

Can operators remain anonymous?

Yes. Operator identification is optional. Workstations can run with a generic login, or operators log in by badge or user account when individual traceability is required.

How are multiple plants handled?

Projects can be exported from one Arkite server and imported on another, so a validated process can be transferred between sites.

Talk to an expert

Review the architecture with our technical team.

We walk through server sizing, network requirements and your integration scenario.

  • A specialist replies to you personally
  • We look at your process, products and systems
  • Together we define a first pilot workstation
Prefer to pick a time? Book a demo