Supervisory security system

spine

Fire · Voice evacuation · Intrusion · Access control · CCTV · Emergency lighting

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.

14makes and channels
< 1 sfrom button press to confirmation from the panel
481 of 481addresses placed automatically on a real drawing
10 yearsof security updates per version
How it works

From existing systems to a live floor plan

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.

Connect

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.

Create points automatically

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.

Place automatically

Spine reads the addresses on the fire drawing and puts the symbols exactly where the consultant drew them.

Monitor and control

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.

Built on top, replaces nothing

The customer's panels keep doing their job. Spine provides the overview and the link between them.

Never in the life-safety path

The fire alarm panel keeps its own path to the alarm receiving centre. Spine is a tool for operations and overview, not alarm transmission.

The panel has the final say

A command only counts as done when the panel itself shows the new state.

Unknown is never shown as green

If Spine does not know the state of a point, it says unknown. A silent connection raises an alarm, not reassurance.

Data stays with the customer

No telemetry and no inbound remote access. Spine works entirely without internet.

AI reads, people decide

An optional AI interface can answer questions but never control anything.

Modules

Three surfaces, one site

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.

Map

The hub. From the map of Sweden down to a single detector on one floor.

  • Map, site, building, floor and symbol in one click
  • Real PDF drawings with live symbols on top
  • Alarms that show the way to the right place
  • 3D view with the floors stacked
  • Calendar for scheduled disablement, conditions and reports
  • Test mode, test plan and test report
licence module: karta

People

One register of everyone who holds a card, across all access control systems at once.

  • The same person in ARX, RCO and Brivo appears as one person
  • Profiles, for example "Finance", that grant the right doors in every system
  • Preview before anything is sent
  • Block a lost card everywhere at once
  • Nightly check that the systems show what was decided
licence module: iam

CCTV

Cameras linked to what they actually see.

  • Video wall from 1×1 to 4×4 with sequencing
  • The camera covering an alarm moves to the top and is marked red
  • A still image is captured when the alarm arrives and is attached to the notification
  • Integrates with the existing video system, no new VMS
licence module: cctv

Add-on: Analysis

licence module: analys

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.

Alarms

The alarm shows the way there

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.

01The map shows where the alarm is02The site and the building light up red03The floor plan opens04The detector pulses, the camera is shown alongside

Screen recording from the demo site Kvarteret Björken, which ships with Spine.

Acknowledge and take ownership

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.
HandleOwnership. Dies with the operator's socket, and then the alarm sounds again. Handover only to a live, authorised session.
Alarm inactiveSilences only your own screen, 30 min default, max 8 h. Notifications are still sent.
StationsLocked view. A wall screen can acknowledge but not handle, and a wall account is not signed out on a timer.
JournalAppend-only JSONL per day, compressed after one week

Notifications to the right person

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.

Alarms that get through, even without an app

new

Alarm page for SMS

An alarm SMS ends with a short link. The page shows the alarm, its current state, the floor plan with the device circled and the camera image. No app and no sign-in are needed to view it.

  • One page per recipientLives for an hour and shows nothing but the alarm
  • Cannot control anythingCommands require signing in to Spine
  • TraceableThe journal shows who opened the link
new

RCS messages

The alarm arrives as a card in the phone's normal messaging app: the sender's logo, the floor plan with the device and then the camera image. A button opens the alarm directly in Spine.

  • Confirmed deliverySpine knows when the message has reached the phone
  • SMS as fallbackPhones without RCS get an SMS with a link to the alarm page

Acknowledging directly from the message is being introduced.

new

Hold-up alarm with location

When a portable hold-up button triggers, the person carrying it gets a link that shares the phone's location. The location appears on the map and in the alarm, with coordinates to read out to emergency services.

  • The alarm says who carries the buttonIts own alarm state, more serious than intrusion
  • Kept only as long as neededUntil the alarm is reset, plus one day

Tested on a real phone: location within 16 metres in seven seconds.

The right alarm, once

  • A fire alarm is always sentMore detectors in the same fire become a follow-up, not a flood of messages
  • Every escalation is sentPre-alarm turning into fire, tamper turning into intrusion: new message and new acknowledgement
  • Pre-alarms go as textShort and fast; the image comes with the fire alarm
  • No duplicatesA reminder about an unacknowledged alarm is sent once

Disablement with a double safeguard

Whoever disables a detector states for how long. Spine re-enables it on the minute, and the fire panel gets the same time in its own timer. If Spine or the connection is down when time runs out, the panel re-enables it itself.

Fast on the phone

The page is stored on the phone. The first start takes around five seconds on a weak connection, the next under a second.

The app

Spine in your pocket, for iPhone and Android

Alarms reach the phone and sound even when it is on silent. From the same app you acknowledge, open doors and disable detectors. The app only talks to your own Spine server.

Android: full-screen fire alarm over the lock screen with the buttons Open Spine, Acknowledge and Silence
AndroidThe fire alarm takes the whole screen, over the lock screen too
iPhone: active fire alarm with camera image and the buttons Acknowledge, Point and On the drawing
iPhoneThe alarm with the camera image, acknowledge right away
iPhone: a door with the buttons Open momentarily, Hold open, Lock until further notice and Release hold
iPhoneControl the door: open, hold open or lock
iPhone: the Right now overview with counts of alarms, faults and disabled points, and the sites in the list
iPhoneThe state right now across all sites
iPhone: searching for door shows the doors in Building A with an Open button on each
iPhoneSearch for a door, detector or place, by text or voice
Android: hold-up settings, the account may raise alarms, alarm key stored, location allowed
AndroidHold-up: a silent alarm with position

Screens from the demo site Kvarteret Björken, shown in Swedish.

Alarms you hear

  • A fire alarm never stops by itselfIt sounds until someone silences it, on silent and through Do Not Disturb too
  • Acknowledge from the phoneWhen the control room acknowledges, the phones go quiet
  • You choose what soundsFire, hold-up, intrusion, doors and faults separately

Control with your fingerprint

Open and hold doors open, disable and enable fire and intrusion. Every command is confirmed with fingerprint or Face ID and goes straight to your own server, never through us.

List or drawing

The list shows the state of all sites, buildings and drawings at once. The drawing view shows the map, the building and the floor plan with the alarming device marked, just as on the computer.

Voice search

Tap the microphone and say "doors floor 3" or "disabled". Speech becomes text on the phone, and only the text goes to Spine as a search. No audio is stored or sent. Search shows things; it never opens anything.

Hold-up

Hold the button for three seconds, in the app, the widget or the quick settings. On iPhone, two presses of the Action button within five seconds is enough. The phone then stays completely silent and sends the alarm and its position every 15 seconds until an operator resets it. Only accounts that have it switched on can raise it.

iPhoneApp Store Android · in reviewGoogle Play

The phone is linked to Spine with a QR code from the computer. Privacy policy for the app

Overview & control

Build your own control view

Every operator, guard and technician can get exactly the picture they need. Most of it is set up directly on the floor plan by selecting symbols.

new

Custom dashboards

Assemble a view from cards: active alarms, a live floor plan, camera, trends, disablements, doors with buttons, calendar, test plan, journal, map and clock.

  • Full-screen wall modeA wall account is not signed out on a timer
  • Detach to another screenThe position is remembered per computer, even after a restart
  • Share with a colleagueAs a copy, or as the role's default
new

Alarm priority 1–5

The most important alarm is always on top. Priority sets the tone, the colour and whether a comment is required on acknowledgement. Priority 5 is information.

  • Per state type or per pointFire and hold-up always have high priority
  • Priority by time of dayFor example intrusion alarms as information during office hours
  • Several alarms in one goAcknowledge or handle several alarms with one shared comment
new

Conditions from the floor plan

Select the symbols and describe the chain: when this door is unlocked and the intrusion area is armed, then show the camera. Only the states and commands the symbols actually have can be chosen.

  • Reverts by itselfWhen the condition ends, the opposite command is sent
  • Survives a restartRe-evaluated without triggering again
new

Calendar posts on the floor plan

A calendar post becomes a symbol. The operator sees at once whether it is active and can run, pause or resume it with one tap, with or without scheduled times.

  • Mixed actions"1 door: hold open · 3 detectors: disable"
  • Optional automatic returnAfter a chosen number of hours
new

Custom symbols and views

Compose your own symbols from the library or upload an image. Each role can get its own start view with zoom, alarm filter and labels, and a mini map shows where on the sheet you are.

new

Reports and trends

Save your own report templates with chosen columns and filters. The report of contaminated detectors shows the worst first. Trends step back through the whole history and are always compared with the period before.

new

Sub-drawings

A floor can have its own detail drawings, for example a plant room or an aspirating detector, up to five levels deep. A link symbol on the floor opens the sub-drawing and lights up in alarm colour when something there is in alarm.

new

Made for tablets

Menus and the alarm bar adapt to screens between phone and desktop, so the whole view fits on a tablet on the wall or in the hand.

new

Says why something is down

A driver that does not respond shows the cause and when the next attempt is made. An acknowledgement counts once, even if someone taps again on a weak connection.

The same word for the same thing, whatever the make. Spine has a shared vocabulary in Swedish and English, with the vendor's own term shown second. An unlocked door has the same name in every access control system.

Auto-create & auto-place

The drawing and the export already know where everything is

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.

Where the points come from

The panel's export file

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 · ARX
Directly from the system

Spine asks the system itself what it contains and creates the points when the driver connects.

Hedengren · RCO · Brivo · Eagle Eye · WAVE
The installer's map

For IO units and building services, the installer writes a simple list of names and addresses.

Generic Modbus
  1. Import the export

    The 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.

  2. Upload the drawing

    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.

  3. Find the addresses

    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.

  4. Find the sections

    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.

  5. Check against the export

    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.

  6. Review and adjust

    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.

OFFICE 2.14 STAIRWELL B 70 70/1270/1370/14 1.6 h section 70 · exists in the panel

Simplified drawing. 70/12 means section 70, address 12. The dashed circle is Spine's section symbol.

481/481addresses on the sheet found in the export
526address texts read on one sheet
1 648detectors, zero deviations from the export
60 fpssmooth zoom on large A1 sheets
69symbols to SB 20.1
0guesses from device names

Measured on a real sheet from a SecuriFire installation.

Review: panel, export, floor plan and Spine side by side new

At a new installation, and every time a new export or floor plan is uploaded, Spine goes through the whole site. The review compares four sources and gives one row per discrepancy, each with a suggested fix.

Panel↔Export↔Floor plan↔Spine
  • Excel for the technicianColour per status, filters, frozen header row and two yellow columns for comment and fixed
  • PDF for the customerDiscrepancies grouped by status
  • Every run is saved as a revisionThe next review shows what is new, what remains and what the technician has fixed
  • Placement overview per panelPlaced out of total, per building, points without a symbol and labels without a point
  • Unknown models are still drawnAs a generic device for the discipline, marked until the right symbol is set
  • Nothing is corrected automaticallyA symbol linked to the wrong point would show a fire in the wrong corridor, so every row is a suggestion for a person

The drawing text is read in the browser with the same reading as auto-placement. Sheets without a text layer show as not read, never as OK. The last 8 revisions are kept. Requires the maintenance level.

Example. The file has two sheets: a summary with counts per status and the list itself.

Placed but does not existOn the plan but not in the exportIn the export but not in the panel Probably renamedDifferent sheet than the planNot placedIn the panel but not in the export Placed, but not on the plan's sheetFixed since lastOK
Symbols, states & commands

What Spine sees and what Spine can do

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.

One symbol, many states

Detector health: spot dirty detectors before they cause false alarms

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.

MakeValuesStatus
Schneider Esmi / EFOContamination 0–100 %, raw value 0–255in service
Hedengren FirescapeContamination, monthly reportlive
Hedengren NeptoluxBattery capacity in minutes, temperaturebuilt
ConsiliumSmoke as % of alarm level, temperature, contaminationbuilt
Securiton SecuriFireSmoke, temperature, CO, contamination, airflow in aspirating pipesplanned
01.014
78 %
02.103
61 %
01.007
44 %
03.021
23 %

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.

Planning & testing

The whole year's testing, planned and proven

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.

1. Plan the year in quarters

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:

  • Select symbols directly on the floor planand choose "add to test plan"
  • Choose from a list: building, floor, devicedevices already tested are marked
  • Add functionsfans, lifts, doors and dampers controlled by the fire alarm
  • Specify what should be disabledfor example alarm transmission and evacuation control, so the test does not start an evacuation
  • Write manual steps and notesfor things done on site

Q1 2027

Building A · Floor 142 devices · 3 functions
2 disabled
Building A · Floor 238 devices

Q2 2027

Building A · Floor 3 part 1/240 devices · 2 functions
1 disabled

Q3 2027

Building A · Floor 3 part 2/239 devices
Garage24 devices · 4 functions
3 disabled

Q4 2027

Building B61 devices · 2 functions

Example. The bar shows how much of the floor has been tested.

2. Carry out the test

  1. Start from the plan

    Choose how long the round should last (default 2 hours, max 12) and whether notifications should be sent during the test.

  2. Spine disables

    What the plan specifies is disabled with the reason "Testing" and automatic re-enable. Everything is journalled.

  3. Everyone can see it is a test

    A yellow-striped banner is shown on every screen.

  4. The technician tests

    Every activation is marked as a test in the report. A real fire alarm still sounds and must be acknowledged as usual.

  5. Spine re-enables

    When the round ends or the time runs out, what Spine disabled is re-enabled, and only that.

Test mode marks, it does not silence

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.

Scopesite:, building: or floor:, any discipline
CheckThe server checks every minute, journal line when the time has run out
JournalKind test, "Test mode ON from plan {name}"
DisablementIf there is no write path the step is marked "manual", and the round starts anyway
API/api/provplan, /forslag, /:id/starta, /api/provning/markera

3. Three ways to "tested"

panelThe panel's test mode

The panel itself reports that the device has been tested, for example Hedengren's walk test.

testLive activation during a round

The device activated while it was in a test round. Also works for makes without a test mode.

manualMarked by hand

Mark one or more devices as tested, with date, note and name. Works without a round in progress.

4. Report and coverage

Tested

With method, time and who.

No activation

Was in the round but never responded. Reveals a faulty detector.

Not tested

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.

Integrations

The makes Spine talks to

Each make has its own package that speaks that system's language. Click a make to see what Spine can do with it.

MakeStatusShows statesControlsCreates pointsAuto-placementMeasured values
YesBuilt, being tested against a real sitePlannedNot applicable
Architecture

One way out of the customer network

Spine is installed on the customer's premises, on an ordinary Windows or Linux 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.

Every command is confirmed by the panel

before = trueAlready done

The state was already the requested one.

before ≠ true · after = trueConfirmed

The panel shows the new state. Measured at 400–640 ms against a real fire alarm panel 400 km away.

after ≠ trueFailed

The state never changed. The operator sees it at once.

Technical

The north link

Transportws:// or wss://, the driver initiates, full resync on every reconnect
AuthenticationA key of its own per driver and per machine, can be made mandatory. For drivers on the server's own machine it is issued with one click. A new key closes the old connection.
Key pinningnorth.pin: pinned, first, off, plaintext
Public addressesUnencrypted ws:// is refused towards public addresses
Rate per socketDriver 2 000 frames/s (burst 8 000), client 100/s, 600 ms CPU/s, max 16 MiB per frame
WatchdogRedials after 100 s without ping
Desired stateThe calendar says what should apply. A driver that has been down gets the command when it comes back up.
Technical

Close codes

CodeCause
4001Frame before hello
4002The frame threw an exception
4003A live id already exists
4008Rate 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
Server requirements

The right server for the site

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.

S

One building

School, office, smaller property

Points
2 000
Clients
5
Cores
2
Memory
4 GB
Disk
40 GB SSD

idle 1 % CPU · 94 MB · 200 events in 3 ms

M

Several buildings

Campus, shopping centre, property company

Points
5 000
Clients
20
Cores
2
Memory
8 GB
Disk
60 GB SSD

idle 3 % · 134 MB, peak 216 MB · connect 0.5 s

L

Large site

Hospital, airport, larger industry

Points
20 000
Clients
100
Cores
4
Memory
16 GB
Disk
120 GB SSD
Network
1 Gbit

idle 17 % · peak 518 MB · 100 clients in 6.6 s · storm 1 000: p50 1.1 s

XL

Portfolio

Municipality or region with many sites

Points
50 000
Clients
100
Cores
8
Memory
32 GB
Disk
250 GB SSD

idle 22 % · peak 829 MB · connect 16 s

Sized together with us.

Applies to all sizes

Operating systemWindows Server x64 or Linux x64 (Ubuntu 24.04 LTS). Runs as a service.
DatabaseNone. A backup is a copy of a folder.
Driver machineAny Windows or Linux computer on the panel's network, about 100 MB memory per driver. Needs no licence of its own.
ClientsBrowser on a computer, wall screen or phone
JournalAbout 150 MB for 13 months at 2 000 events per day
RedundancyThrough virtualisation: the server moves between hosts. Active/active clustering is not yet supported.
Technical

Ports and operation

18080Operator interface, the drivers connect here
18081Analysis (MCP), loopback by default, 0 = off
18078Status page, read only
18079Control port, loopback only
Memory~100 MB + 10 MB per 1 000 points at idle, double at peak
In service2 415 points, 7 drivers: 145 MB flat over 8 h, event loop p95 27 ms
PackagesFull package with embedded Node 24. Updates can be delivered as a delta of a few MB.
For the IT department

What IT needs to know before installation

Spine is built to fit an IT environment with strict requirements. Nothing listens in the panel networks, nothing phones home and nothing requires internet access.

Network and firewall

To the serverOne port, 18080 TCP, from stations and drivers. HTTPS and WSS when encryption is on.
Panel networksNothing inbound. The driver connects out to the server, and to the panel on the manufacturer's port, for example OPC UA or Modbus TCP.
InternetNot required. Only needed for cloud-based systems and for notifications by e-mail, SMS or Teams.
TelemetryNone. No remote access into the site.
Local only18078 status page, 18079 control port. 18081 analysis, off by default.

Virtualisation and clusters

PlatformA standard virtual Windows or Linux server, for example on VMware or Hyper-V
Moves in a clusterSupported. The licence follows live migration and restart on another host. Copying the server to a new machine does not work.
High availabilityThrough the hypervisor. Spine runs as one instance; active/active with two servers is not supported yet.
After a restartThe service starts by itself, the drivers reconnect and send the full state. Schedules missed during the outage are applied at once.
BackupNightly or weekly at a chosen time, with separate weekly copies and their own retention. Restore takes about two hours.
Dead man's switchSpine calls an address in your monitoring at regular intervals. If the calls stop, you know Spine has stopped.

The fire panel's own path to the alarm receiving centre is always independent of the Spine server.

Sign-in and two-factor authentication

AccountsLocal register. Passwords are stored only as scrypt hashes. The session is a random token in an HttpOnly cookie; the file on disk holds only its hash.
Two-factorAuthenticator app (TOTP, for example Microsoft Authenticator), SMS code or passkey. Eight backup codes.
Forgotten passwordA one-time link to the account's email or mobile, or one of five recovery codes that work without email or SMS. A password change ends all sessions.
PasskeySign-in with a passkey alone, without a password
RequirementPer account or for the whole installation: none, administrators only, or everyone
LockoutFive failures in a row lock the account for 15 minutes, both configurable. The attempts raise an intrusion alarm that can go out as a notification. Unknown names get the same answer as locked ones
SessionsEnd after a configurable idle time (default 12 hours) or a maximum length (default 30 days)
LockdownA session or a person can be locked at once, for example under threat

AD and Entra ID planned

Sign-in against the customer's directory is coming as a complement to the local register.

  • AD via LDAP, Entra ID via OpenID ConnectUsers sign in with their normal accounts
  • Same permission modelThe directory grants the same per-discipline rights and management level a local account has today
  • Two-factor per your policyWith Entra ID, the organisation's own sign-in requirements apply
  • Local accounts always remainA directory outage must never lock an operator out during a fire alarm

Permissions

Per disciplineView, operate, engineer or administrator, separately for all seven disciplines. Custom roles can be created.
ManagementOperator, maintenance (floor plans, symbols, drivers) or system owner
Per buildingAn account sees only the buildings it has rights to. Filtered on the server.
Start viewEach role can get its own start view and dashboard
StationsWall screens with a locked view. A wall account is not signed out on a timer.
First startOpen until the first administrator is created, with a clear warning. Create the administrator right at installation.

Encryption, operation and updates

EncryptionHTTPS and WSS on the same port. A certificate is created automatically, or yours is used. Drivers pin the server's key.
SecretsPanel passwords are kept out of the configuration: encrypted with DPAPI on Windows, in a file only the service can read on Linux
ServiceWindows service or systemd on Linux. Starts without sign-in and restarts on failure
UpdatesA signed package is uploaded once, and each machine updates from the server. Unsigned packages are refused. Nothing is downloaded from the internet.
RollbackVersions sit side by side. A version that fails to start is replaced automatically by the previous one.
DataStored locally on the server. No database to operate.

Server guard new

A small service next to Spine that blocks suspicious addresses in the server's own firewall. It reads Spine's journal and the operating system's security log, so it also sees attempts against remote desktop and file shares.

  • Starts in dry-run modeShows what it would have blocked before it blocks for real
  • Time-limited blocksThe time doubles for anyone who comes back. Everything is in the journal.
  • Installs with one clickDownloaded pre-configured from the settings, for Windows and Linux
  • Safety nets that cannot be switched offLocal addresses are never blocked, an address that has just signed in correctly to Spine is protected, and a stop file lifts all blocks at once

Notification channels are monitored new

Spine shows for each channel (RCS, SMS, push, email, webhook and Teams) when it last worked. If a channel fails, the row turns red and the administrator gets a system notification, before the next alarm needs to go out.

RCS delivery is checked after every send.

Testing & validation

Every fix proven, every release checked

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.

340+test files run before every release
24review rounds: source code and penetration tests
6real systems tested: fire, access control, cloud
0known vulnerabilities in the dependencies at build
  • Against real panels

    Disable and enable on a real fire alarm panel, doors in real ARX, RCO and Brivo systems, Hedengren against the cloud.

  • All the way to the screen

    Tests run from the panel's file through driver and server all the way to a real browser.

  • Vendor specifications as simulators

    Before a panel is on site, the driver is tested against a simulator built from the vendor's protocol description.

  • Randomised event sequences

    Tests generate thousands of random alarm sequences and check that an alarm never disappears without a journal entry. The driver interface is fed malformed and broken messages.

  • Every way in is checked

    A table lists every way into the server and the permission each one requires. A test reads the code and stops the build if a route lacks its check.

  • Makes are kept apart

    A dedicated test stops the build if something that belongs to only one make ends up in the shared code.

  • Load and capacity

    A rig builds sites of up to 50 000 points and 100 clients and measures every release.

  • Security reviews

    Spine has been through 24 review rounds: 16 reviews of the full source code by an independent AI reviewer and 8 penetration tests against a live server with accounts at every level. More than 190 findings are fixed, each with a test that fails without the fix. The latest tests found nothing critical and nothing high. An external independent review is being prepared.

Rules that apply to all code

  • Every fix gets a testThe bug is reintroduced on purpose and the test must fail. Only then does the fix count.
  • Unknown is never greenTests require that anything that could not be read is shown as unknown, never as normal.
  • Load is measured, not assumedHow hard Spine polls a panel is measured on the wire.
  • The build stops on vulnerabilitiesCritical and high findings in dependencies stop the build.
  • Every package is signedA package with the wrong signature is never installed.
  • The manual is tested against the codeThe Swedish and English versions must not drift apart.
Technical · assertions per test suite
CRA & GDPR

Built for the regulations from the start

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.

Cyber Resilience Act EU 2024/2847

The regulation requires secure development, vulnerability handling and security updates throughout the product's lifetime.

  • Bill of materials in every packageAn SBOM in CycloneDX format lists all components
  • Signed updatesTwo keys, checked on the machine doing the install. Unsigned is refused
  • 10 years of security updatesThe support period is stated in the product
  • Updates are never blocked by the licenceAn expired licence does not stop a security update
  • Contact route for vulnerabilitiessecurity.txt and SECURITY.md in every installation
  • CRA documentation from the installationVersion, build number, keys and encryption state per connection
11 Sep 2026Reporting of actively exploited vulnerabilities
11 Dec 2027Full application and CE marking

Own assessment: important product class I (Annex III p. 1). No formal ruling yet. Remaining: Annex VII documentation, declaration, TLS by default.

GDPR EU 2016/679

The customer is the data controller. Spine helps the customer keep things in order and show what is held.

  • Everything stays with the customerNo telemetry. Spine never contacts the vendor on its own.
  • Only what is neededName, department, contact details, card and validity period. Personal identity numbers are not stored.
  • Retention limits by defaultJournal 400 days, deregistered people 90 days, images 90 days. All configurable.
  • A person card per individualShows everything Spine holds about a person, making subject access requests easier
  • Passwords and PINs are protectedPasswords are stored only as a hash. A PIN is never shown afterwards.
  • Input for the record of processingSpine generates Article 30 documentation in Swedish and English

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.

Sign-in and permissions

Two-factor sign-inCode in app, SMS code, passkey and backup codes
RolesPer discipline: read, operate, technician, administrator, or custom roles
Per buildingThe operator only sees the buildings they are authorised for
ManagementSeparate day-to-day operation (floor plans, symbols) from system responsibility
LicenceWorks fully offline. Moves with a migration, but cannot be cloned.
Technical

Security in detail

Accountsscrypt, HttpOnly session, growing delay on failed attempts, same response time for known and unknown names, TOTP RFC 6238
LicenceEd25519, 2 of 3 machine identifiers. An expired licence blocks commands, never monitoring.
PackagesEd25519, SBOM CycloneDX, npm audit stops the build, 4 runtime dependencies
VersionsSide by side. Three crashes within 3 min start the previous version.
CSPStrict by default: script-src 'self', object-src 'none'
Rate limitsLimits on the API, sign-in, SMS and connections per address
MCPJSON-RPC 2.0, seven read-only tools, every call is journalled
Roadmap

What exists and what is coming

Spine is developed at a fast pace with frequent releases. The current version is 0.139.0.

Available

  • Auto-created points and auto-placement
  • Calendar, conditions and scheduled disablement
  • Test mode and Q1–Q4 test plan
  • People across several access control systems
  • Notifications with images: push, Teams, SMS, email
  • 3D view of the building
  • Detector health with trend
  • Reconciliation report between export, symbols and drawing
  • Notification-only accounts
  • RCS messages and alarm page for SMS
  • Hold-up alarm with shared location
  • Linux server
  • Custom roles and forgotten password
  • A key per driver
  • Alarm priority 1–5 and multi-select
  • Custom dashboards and wall mode
  • Conditions and calendar posts on the floor plan
  • Custom symbols and start views
  • Report templates and trends back in time
  • Account lockout and intrusion alarm
  • Server guard
  • Monitoring of notification channels
  • Shared vocabulary for all makes
  • Sub-drawings in five levels
  • Tablet layout

In progress

  • Hanwha Wisenet WAVE
  • Securiton SecuriFire and Consilium
  • IO units via Modbus
  • Acknowledge directly in RCS
  • Buy time during alarm delay

Planned

  • AD and Entra ID
  • BACnet, Milestone, ONVIF
  • Voice evacuation
  • Axema, Partnersec, Traka Web
Technical · drivers in the test installation 30 Sep 2026
anlaggningen

Sites, buildings, floors and panels

drivrutinernas_lage

Connections, versions and load per path

punkternas_lage

Points and states with filters

las_journal

The journal as structured rows

provningstackning

Tested and untested points

avvikelser

Decided versus actual permissions

underlag

GDPR, CRA and operations documentation