All your security systems in one picture. Spine connects fire alarm, intrusion alarm, access control, cameras and emergency lighting, whatever the make, and shows everything on the building's own floor plans.
A top layer over existing panels. Per-make drivers dial out to a site server, every point gets a stable id and every command is confirmed by read-back from the panel.
The customer does not need to replace any panels. Spine reads what is already there, builds the site by itself and makes it controllable from one place.
A small piece of software is connected to each existing panel or access control system. It contacts Spine outbound, so the customer's network never has to be opened inbound.
Every detector, door and camera is created from the panel's own export file or directly from the system. Nobody types in thousands of addresses by hand.
Spine reads the addresses on the fire drawing and puts the symbols exactly where the consultant drew them.
Alarms, faults and disablements show up directly on the floor plan. The operator can reset, disable and open doors, and the panel confirms every action.
The customer's panels keep doing their job. Spine provides the overview and the link between them.
The fire alarm panel keeps its own path to the alarm receiving centre. Spine is a tool for operations and overview, not alarm transmission.
A command only counts as done when the panel itself shows the new state.
If Spine does not know the state of a point, it says unknown. A silent connection raises an alarm, not reassurance.
No telemetry and no inbound remote access. Spine works entirely without internet.
An optional AI interface can answer questions but never control anything.
Spine is made up of modules that are licensed separately. A module that is not included does not appear at all. All modules share the same floor plans, the same journal and the same permissions.
The hub. From the map of Sweden down to a single detector on one floor.
One register of everyone who holds a card, across all access control systems at once.
Cameras linked to what they actually see.
Ask an AI assistant questions about the site, for example which detectors have not been tested this year. The assistant can only read. Without the module there is no AI interface at all, so the customer can show that no AI touches their data.
A fire alarm takes the operator from the map, via the site and the building, to the detector in alarm on the floor plan. The journey takes a couple of seconds and can be cancelled with one click.
Screen recording from the demo site Kvarteret Björken, which ships with Spine.
Acknowledge means you have seen the alarm. Handle means you take responsibility for it. If the person handling it loses the connection, the alarm sounds again, so no alarm is ever left without an owner.
| Acknowledge | "Seen". Can require a statement or a checklist. |
|---|---|
| Handle | Ownership. Dies with the operator's socket, and then the alarm sounds again. Handover only to a live, authorised session. |
| Alarm inactive | Silences only your own screen, 30 min default, max 8 h. Notifications are still sent. |
| Stations | Locked view and timeout. A wall screen can acknowledge but not handle. |
| Journal | Append-only JSONL per day, compressed after one week |
Each user chooses which alarms, which buildings and which times should trigger a notification, and how. An image from the camera or the floor plan is attached.
The consultant's fire drawing and the panel's export describe the same building. Spine reads both and builds the site by itself. What used to take days of manual work takes minutes.
Spine reads the export file from the panel's programming tool and creates every detector, section and control output. Works before the panel is even connected.
EFO · SecuriFire · Consilium · ARXSpine asks the system itself what it contains and creates the points when the driver connects.
Hedengren · RCO · Brivo · Eagle Eye · WAVEFor IO units and building services, the installer writes a simple list of names and addresses.
Generic ModbusThe points are created with the same id the panel will report later. They show grey as planned until the panel responds.
Id: <driver>/<kind>/<address>. At handover the panel's list applies, and everything is journalled.
The fire drawing as a PDF, the same file that is printed and handed to the fire and rescue service.
Vector PDF with a text layer is required for auto-placement. Scanned sheets are displayed and placed by hand. No OCR. Page 1 only.
Spine finds every address text on the drawing, for example 01.001 or 70/12, and places the symbol where the consultant drew the detector.
EFO ^\d{1,2}\.\d{2,3}$, SecuriFire ^\d{1,4}/\d{1,3}$. The symbol is placed 1.6 label heights below the label centre. Rotated sheets are handled.
Large section numbers in circles get Spine's section symbol on top of the consultant's circle.
Conditions: at least twice the size of the address label, more than 8 % from the edge, and the section exists in the driver.
Every address must exist in the panel's export. Spine never guesses from names.
No confidence score, only exact matches. The same address in several places becomes several devices with the same id.
Everything can be moved, rotated and scaled in the same editor. A new drawing only moves what Spine placed itself, and hand-placed symbols are left untouched.
Simplified drawing. 70/12 means section 70, address 12. The dashed circle is Spine's section symbol.
Measured on a real sheet from a SecuriFire installation.
The symbols follow the Swedish standard SB 20.1, so the drawing looks the way the fire and rescue service is used to. The catalogue has 69 symbols. The colour shows the state and the shape shows what equipment it is.
Modern detectors measure all the time. Spine reads the values, stores a trend per detector and lists the dirtiest first, so service staff can replace the right detector in time.
| Make | Values | Status |
|---|---|---|
| Schneider Esmi / EFO | Contamination 0–100 %, raw value 0–255 | in service |
| Hedengren Firescape | Contamination, monthly report | built |
| Hedengren Neptolux | Battery capacity in minutes, temperature | built |
| Consilium | Smoke as % of alarm level, temperature, contamination | built |
| Securiton SecuriFire | Smoke, temperature, CO, contamination, airflow in aspirating pipes | planned |
Example. Step curve per detector, change over the last 30 days.
Spine does not judge the values itself. Limits are only set where the manufacturer specifies them. Otherwise the value is shown neutrally.
Fire alarms must be tested regularly, and not just the detectors. Fans, lifts, doors and dampers controlled by the fire alarm must also work. Spine plans the year, disables what must not activate during the test and writes the report while the technician walks round.
Spine suggests a Q1–Q4 split that covers the whole site in one year. The suggestion goes floor by floor, splits large floors and evens out the quarters. You can also choose yourself:
Example. The bar shows how much of the floor has been tested.
Choose how long the round should last (default 2 hours, max 12) and whether notifications should be sent during the test.
What the plan specifies is disabled with the reason "Testing" and automatic re-enable. Everything is journalled.
A yellow-striped banner is shown on every screen.
Every activation is marked as a test in the report. A real fire alarm still sounds and must be acknowledged as usual.
When the round ends or the time runs out, what Spine disabled is re-enabled, and only that.
An alarm during a test sounds, escalates and is recorded in the journal as an alarm. The test is written as a separate line alongside. This means testing can never hide a real fire.
| Scope | site:, building: or floor:, any discipline |
|---|---|
| Check | The server checks every minute, journal line when the time has run out |
| Journal | Kind test, "Test mode ON from plan {name}" |
| Disablement | If there is no write path the step is marked "manual", and the round starts anyway |
| API | /api/provplan, /forslag, /:id/starta, /api/provning/markera |
The panel itself reports that the device has been tested, for example Hedengren's walk test.
The device activated while it was in a test round. Also works for makes without a test mode.
Mark one or more devices as tested, with date, note and name. Works without a round in progress.
With method, time and who.
Was in the round but never responded. Reveals a faulty detector.
Shown as a dashed circle on the floor plan until it has been tested.
Each floor gets an "n of m tested" bar. The report is downloaded as CSV or PDF per calendar year or rolling 12 months, and older periods can be opened afterwards.
Each make has its own package that speaks that system's language. Click a make to see what Spine can do with it.
| Make | Status | Shows states | Controls | Creates points | Auto-placement | Measured values |
|---|
Spine is installed on the customer's premises, on an ordinary Windows server. The small piece of software at each panel dials out to the server. That is why no ports need to be opened inbound to the panels' network, which most IT departments require.
The same code runs on one machine or split. Only the driver configuration differs. On-prem is primary and Spine can run entirely without internet.
Fire, intrusion, access control, emergency lighting, cameras, IO
One per make, in its own process. A crash affects nothing else.
Holds the state, the calendar, the journal and the permissions.
Nothing to install. Works as an app on the phone with push.
The state was already the requested one.
The panel shows the new state. Measured at 400–640 ms against a real fire alarm panel 400 km away.
The state never changed. The operator sees it at once.
| Transport | ws:// or wss://, the driver initiates, full resync on every reconnect |
|---|---|
| Authentication | Shared token, compared in constant time. An allowlist of known drivers can be switched on. |
| Key pinning | north.pin: pinned, first, off, plaintext |
| Public addresses | Unencrypted ws:// is refused towards public addresses |
| Rate per socket | Driver 2 000 frames/s (burst 8 000), client 100/s, 600 ms CPU/s, max 16 MiB per frame |
| Watchdog | Redials after 100 s without ping |
| Desired state | The calendar says what should apply. A driver that has been down gets the command when it comes back up. |
| Code | Cause |
|---|---|
4001 | Frame before hello |
4002 | The frame threw an exception |
4003 | A live id already exists |
4008 | Rate exceeded |
// the point id is the whole contract arx-1/door/17 efo-1/p0/01.001 cons-1/u2/10/10 // the agent's remote control of drivers agentCmd { reqId, op, what, by, args } → agentResult
Spine needs no database and no special hardware. An ordinary virtual Windows server is enough. The recommendations below include headroom. The measurements come from a load rig on 2 cores.
School, office, smaller property
idle 1 % CPU · 94 MB · 200 events in 3 ms
Campus, shopping centre, property company
idle 3 % · 134 MB, peak 216 MB · connect 0.5 s
Hospital, airport, larger industry
idle 17 % · peak 518 MB · 100 clients in 6.6 s · storm 1 000: p50 1.1 s
Municipality or region with many sites
idle 22 % · peak 829 MB · connect 16 s
Sized together with us.
| Operating system | Windows Server x64. Runs as a Windows service. |
|---|---|
| Database | None. A backup is a copy of a folder. |
| Driver machine | Any Windows computer on the panel's network, about 100 MB memory per driver. Needs no licence of its own. |
| Clients | Browser on a computer, wall screen or phone |
| Journal | About 150 MB for 13 months at 2 000 events per day |
| Redundancy | Through virtualisation: the server moves between hosts. Active/active clustering is not yet supported. |
18080 | Operator interface, the drivers connect here |
|---|---|
18081 | Analysis (MCP), loopback by default, 0 = off |
18078 | Status page, read only |
18079 | Control port, loopback only |
| Memory | ~100 MB + 10 MB per 1 000 points at idle, double at peak |
| In service | 2 415 points, 7 drivers: 145 MB flat over 8 h, event loop p95 27 ms |
| Packages | Server ~66 MB with embedded Node 24, driver ~43 MB |
A system that controls fire alarms and doors must not guess. That is why the code is tested in several layers, against real panels and against the vendors' own specifications.
Disable and enable on a real fire alarm panel, doors in real ARX, RCO and Brivo systems, Hedengren against the cloud.
Tests run from the panel's file through driver and server all the way to a real browser.
Before a panel is on site, the driver is tested against a simulator built from the vendor's protocol description.
A dedicated test stops the build if something that belongs to only one make ends up in the shared code.
A rig builds sites of up to 50 000 points and 100 clients and measures every release.
Recurring reviews of the server, the drivers, the web interface and the packages. An external penetration test is planned for autumn 2026.
The EU Cyber Resilience Act sets requirements for all products with digital elements. The General Data Protection Regulation governs how personal data in access control systems is handled. Spine is built for both and produces the documentation itself.
The regulation requires secure development, vulnerability handling and security updates throughout the product's lifetime.
Own assessment: important product class I (Annex III p. 1). No formal ruling yet. Remaining: Annex VII documentation, declaration, TLS by default.
The customer is the data controller. Spine helps the customer keep things in order and show what is held.
Secrets for the vendor systems are encrypted with DPAPI. The journal cannot be edited. Corrections are made with a new line. Data processor only under a support agreement with access.
| Two-factor sign-in | Code in app, SMS code, passkey and backup codes |
|---|---|
| Roles | Per discipline: read, operate, technician, administrator |
| Per building | The operator only sees the buildings they are authorised for |
| Management | Separate day-to-day operation (floor plans, symbols) from system responsibility |
| Licence | Works fully offline. Moves with a migration, but cannot be cloned. |
| Accounts | scrypt, HttpOnly session, lockout after 5 failures, TOTP RFC 6238 |
|---|---|
| Licence | Ed25519, 2 of 3 machine identifiers. An expired licence blocks commands, never monitoring. |
| Packages | Ed25519, SBOM CycloneDX, npm audit stops the build, 4 runtime dependencies |
| Versions | Side by side. Three crashes within 3 min start the previous version. |
| CSP | script-src 'self', object-src 'none' |
| MCP | JSON-RPC 2.0, seven read-only tools, every call is journalled |
Spine is developed at a fast pace with frequent releases. The current version is 0.139.0.
anlaggningenSites, buildings, floors and panels
drivrutinernas_lageConnections, versions and load per path
punkternas_lagePoints and states with filters
las_journalThe journal as structured rows
provningstackningTested and untested points
avvikelserDecided versus actual permissions
underlagGDPR, CRA and operations documentation