---
title: On-premise local historian
slug: concepts/on-premise-local-historian
docTags: 
createdAt: 2025-09-26T09:05:07.380Z
---

A single Factry Historian instance runs locally within the production site, collecting and storing data close to the machines. It can't be simpler.

It is a straightforward setup most common in single-site companies, or when the focus is on reliable local data collection without the need to share across multiple plants.

## When it’s used

- For standalone factories without a corporate-wide historian strategy
- When production data must stay entirely on-premise (e.g. due to regulation, IT policies, or latency constraints)
- In cases where local operators, engineers and managers need fast, direct access to process data
- As a first step toward digitalization before scaling to multi-site or cloud architectures

## Architecture

Factry Historian runs on a server or virtual machine inside the plant network.

Collectors interface directly with PLCs, SCADA, or other OT data sources.

All data is written and stored locally; there is no dependency on external networks.

Dashboards, reporting, and APIs are served directly from this local instance.

::Image[]{src="https://app.archbee.com/api/optimize/SMPo4IS9FkillUAMsur2c/Gtx-B6lHU3U9ALmpc8wzP-20250926-091640.png" darkSrc="https://archbee-image-uploads.s3.amazonaws.com/SMPo4IS9FkillUAMsur2c/Gtx-B6lHU3U9ALmpc8wzP-20250926-091640.png" size="24" width="3343" height="1196" darkWidth="3343" darkHeight="1196" position="center" caption="On-premise local historians" showCaption="true"}

## Functions used

- Collectors buffer data locally and write it into the on-premise historian database
- Users manage configuration and access dashboards directly from the same server
- \[Optional] Integrations with local MES, ERP or lab systems can be made on-site

## Benefits

- The site is not reliant on internet or WAN connectivity
- Low latency access to live and historical data
- Simple to manage: one installation, one site, one team
- Sensitive process data never leaves the factory network
- Good entry point for companies starting their Industry 4.0 journey

## Considerations

- Scaling is limited to the capacity of the local server (storage, CPU, redundancy)
- Requires on-site IT/OT support for maintenance, backups and upgrades
- No built-in sharing of data across sites: each historian remains an island

## Summary

A local on-premise historian deployment: simple, self-contained, and reliable.
Ideal for single-site factories or as a first step before scaling to [centralized](docId\:K-dhAgxCRdXAhJCsmEKnr) or [multi-tier](docId:9KahOR-4WZAwYRmu8nXmL) architectures.