Which one am I running? The version is shown in the footer of the sign-in page and on the dashboard. It is read from the server each time, so it is what is actually running rather than something written into a page.
There is one release channel. There is no beta, no nightly and no per-customer build. Cairn never updates itself and never checks whether an update exists — it makes no outbound call at all — so a release reaches an installation only when an administrator puts it there.
How to apply one. Replace the supplied folder with the newer package, keeping your data folder, host-secrets folder and configuration files, then run the upgrade for your platform: upgrade.ps1 on Windows, or sudo /opt/cairn/linux/upgrade.sh on a Linux server, as the runbook says. Either one checks the new package's checksum before anything else, then that there is room for the backup and the new images, takes and verifies a full backup, loads the new images, recreates the containers against your existing data, waits for Cairn to answer and reports the version then running. Installing offline is supported throughout. Open a Project after any upgrade and confirm it opens before relying on it.
Security-critical releases carry a badge below. Apply one promptly. Each entry also states, in three short answers, what the release means for the data already on disk — because reverting a package reverts the software and never the data.
Where an answer could not be established from the source, the runbook or the upgrade script, it is written Not assessed rather than guessed at. Take the backup the upgrade offers, every time.
1.0.0-rc1 18 October 2026 Security-critical
Before you upgrade
- No renewal of the installation acknowledgements is needed: their wording has not changed.
- The upgrade checks there is room for its backup and the new images before it changes anything, and if there is not, refuses with the figures (exit 32 on Linux).
- If this installation's recovery key was never confirmed as stored, run the upgrade in a window you are watching. It shows the key and waits while you store it. The runbook's "Two checks before every upgrade" says how to read that state.
- On Linux, take a fresh backup once the upgrade has finished. The backup the upgrade takes first is made by the version you are leaving, which leaves some panorama photographs out (see Known limits).
Security
- Both installers, and the Linux manual unlock, show the recovery key only at a terminal. Run any other way, they stop before changing anything.
Changed
- A client account's viewer has the section box and colour by true colour, elevation, intensity and classification. A share link's viewer can save views and section boxes, and lists the saved ones.
- The licence notices name the components that ship with no licence recorded, and what the bill of materials leaves out.
- These release notes say how to apply a release on a Linux server as well as on Windows.
Fixed
- After a restore on Linux, every scan whose converted point cloud was not in the backup is marked for Retry, as the runbook says.
- Importing a model over the one a project has no longer deletes it when the new file is refused, and keeps the replaced model for 7 days, as removing it does. Converting a model again always converts the current one.
- Importing panoramas, or a NavVis walk, over the ones a project already has no longer writes over them: the replaced images are kept for 7 days, as removing them does, and an import that is refused or fails part way changes nothing. Removing panoramas twice in the same second no longer loses the first set's copies.
- A Linux backup now carries every panorama photograph. Before, it left out a NavVis walk's photographs and the panoramas extracted from an E57; a restore from such a backup brought those stations back without an image.
- Converting a model again while it is still converting is refused, rather than starting a second conversion. An upload over a model that is removed while the upload arrives is refused with a clear message. Files left by an upload that a server stop interrupted are set aside at the next start and reclaimed after 7 days.
- These notes: 0.3.0-pilot.18's said no screen shows the installation-wide list of share links to a surveyor. The dashboard's Share links view does.
Known limits
- A backup made on Linux by an earlier version lacks NavVis walk photographs and the panoramas extracted from an E57, until a fresh backup is taken with this version. A restore from one brings those stations back without an image.
- Converters run as Cairn's own user. The programs that read uploaded scans and models run with the same rights as Cairn itself, so a file crafted to take one over could read Cairn's own files, including its key files. Uploading needs a surveyor or administrator account. To be fixed after version 1.
- A second visit to a project downloads its point cloud again. Browsers do not reliably keep the cloud between visits, so reopening a project is not faster than the first visit.
- On a phone, colour offers three modes: true colour, elevation and intensity. Colour by scan and by classification are on larger screens only.
- Docker only. Version 1 installs with Docker on Windows or Linux. Running Cairn as a plain service without its container is not supported.
- Many projects show a coordinate warning. Cairn reads no coordinate system from a model file, so a project with a model always lists the model as declaring none.
- Data deleted or replaced inside a project cannot be restored from Cairn. It is kept on the server for 7 days, then removed; a whole project deleted to the recycle area can be restored for 14 days.
- The Navisworks export does not work through a share link, and the volume box measurement has no button yet.
- An administrator has no sign-out button on the dashboard.
- A structured E57 holding several setups shows one scan station; export one setup per file.
Data compatibility
- Existing project data opens unchanged; nothing in a project is rewritten.
- Rolling back to 0.3.0-pilot.19 still reads the data: no stored format changed. What this version sets aside when an import replaces something goes into the same 7-day folders a removal writes, which that version also clears after 7 days.
- Rolling back further, to 0.3.0-pilot.18, reads the data as 0.3.0-pilot.19's notes say: a quality-control statement and its matches stay in the project, with no screen for them.
0.3.0-pilot.19 13 October 2026 Security-critical
Before you upgrade
- No renewal of the installation acknowledgements is needed: their wording has not changed.
- Check there is room for the backup the upgrade takes first: at least the size of your newest backup, plus about 3 GB for the new image. Neither upgrade script checks it.
- If this installation's recovery key was never confirmed as stored, run the upgrade in a window you are watching. It shows the key and waits while you store it. The runbook's "Two checks before every upgrade" says how to read that state.
Security
- An upgrade shows the encryption recovery key only to a person at the screen. Run in the background, or with its output going into a file, an upgrade that would have to show the key now stops before it changes anything and says to run it again in a window; before, it could write the key into that file.
- Every refusal of a client account is its route's own rule, and each route's answer to a client account is fixed by a test, instead of resting on one check in front of every route.
New
- Quality control against survey control, on screen. A surveyor ticks "Control and point cloud use the same coordinate system", picks each control point's match in the cloud, and reads and downloads the residual report.
- A warning when coordinate systems are missing or differ. When a dataset in a project declares no coordinate system, or two declare different ones, the viewer says so and names what each declares. The data still loads, shown as supplied, without conversion. Cairn reads no coordinate system from a model file, so a project with a model always shows the warning.
- Three short guides, in the package's guides folder: one for the administrator, one for surveyors, and one page to pass on with a share link.
Changed
- A surveyor may set a project's coordinate zone and its delivery state, and see a share link's QR image, as an administrator can.
- The dashboard's line about scan stations far apart now states only the distance; it no longer suggests the scans use different map zones.
- Version 1 installs with Docker only. Running Cairn as a plain service without its container is not supported.
- The runbook's office server installation is rewritten for a first install from the runbook alone, and its Windows steps are corrected: the recovery key is shown while the installer runs, an 8 GB PC needs Docker given more memory first, and a Windows backup carries the converted point clouds.
Improved
- The image is built from fixed versions of its base images, so rebuilding this release ships the same system packages.
Fixed
- A DXF model stopped for memory or time can be converted again in place, as IFC and LandXML models can, without uploading it again.
Known limits
- After a restore on Linux, scans come back without their converted point clouds and are not offered for conversion again. A Linux backup leaves the converted clouds out to save space, and this version does not mark the restored scans for Retry. A Windows backup carries them, so a Windows restore is not affected.
Data compatibility
- Existing project data opens unchanged; nothing in a project is rewritten.
- Rolling back to 0.3.0-pilot.18 still reads the data: no stored format changed. A quality-control statement and the matches made in this version stay in the project; 0.3.0-pilot.18 has no screen for them.
0.3.0-pilot.18 10 October 2026 Security-critical
Before you upgrade
- No renewal of the installation acknowledgements is needed: their wording has not changed.
- Cairn no longer uses swap. Its swap limit is now its memory limit, so a job too big for the memory Cairn has is stopped at once, with a plain message, instead of slowing the whole machine first. A conversion that only fitted by using swap may now be refused: give Cairn more memory (CAIRN_MEMORY_LIMIT in this folder's .env) or split the scan.
Security
- The converters no longer receive the server's secrets. The programs that read uploaded scans and models start with only the settings they need, so a file crafted to take one over could not read the server's own credentials from it.
- A bad or oversized model can no longer stop Cairn. IFC, DXF and LandXML files are converted in a process of their own, which is stopped alone if it needs more than half of Cairn's memory or runs past 60 minutes; the server and every other project carry on. If memory does run out, the operating system now stops a converter rather than the server.
- A failed conversion no longer shows internal detail. The scan says in plain words what failed and what to do; the tool's command line and output, which could include internal paths and the cloud's coordinates, go only to the server's own log.
- The access log and the diagnostics no longer record project names or uploaded file names; they use each project's identifier.
New
- A serious failure stays on screen until someone deals with it. System Health raises a notice when something serious breaks, even if nobody was looking at the time, and keeps it after the fault clears until an administrator or a surveyor dismisses it. The dismissal records who and when; without accounts, the operator types their own name.
Changed
- A surveyor can open the diagnostics in System Health, build the diagnostics bundle and read the access summary, as an administrator can. Including project names in a bundle is still asked each time and defaults to no.
- A surveyor may read the installation-wide list of share links, as an administrator can. No screen shows that list yet.
- The service unit for running without Docker (DEPLOY.md) no longer fixes Cairn's memory at 6 GB.
Improved
- Each line of the access log records how long the request took.
- The bill of materials is written by the image it describes, and the package carries that file.
Fixed
- The access log survives an upgrade, a backup and a restore; it was lost each time the container was replaced.
- Removing a section box you had set and placing a new one gives the new box its handles, and the hint is right after Set.
Data compatibility
- Existing project data opens unchanged; nothing in a project is rewritten.
- The access log now lives in the data folder (_cairn/access-log), with the failure notice beside it (_cairn/operator-notice.json); both are in every backup. Upgrading from an earlier release copies the old access log there first, and a file already there is never overwritten.
- Rolling back to the previous version still reads the data. That version writes its access log inside its container again, and shows neither the log in the data folder nor the failure notice.
0.3.0-pilot.17 5 October 2026
Before you upgrade
- Cairn now sizes its memory to the machine. The installer and the upgrade give Cairn this machine's memory less 2 GB and print the figure they chose; on Windows the machine is Docker Desktop's virtual machine. To choose a figure yourself, put CAIRN_MEMORY_LIMIT (for example 12g) in this folder's .env. On a machine with less than about 4 GB the installer refuses, and says why.
New
- Deleted and disconnected projects have a screen of their own. The dashboard's recycle area lists each deleted project, which can be restored there for 14 days; only an administrator can delete one permanently before then, after typing its name. Disconnected projects are listed beside it, to reconnect.
- Setup, and the renewal of the installation acknowledgements, show how the encryption key is kept and recovered, beside the acknowledgement that a recovery copy is held outside the machine. The key itself is never shown on the page.
Changed
- A surveyor can restore a deleted project and reconnect a disconnected one, as an administrator can. Deleting a project permanently is still an administrator's alone.
- A project that declares no map zone is no longer placed by assuming one, which could draw it hundreds of kilometres from the site. The dashboard map shows no survey-data pin for it and says "location unknown: set the zone or click to place"; a pin placed by hand still shows. The viewer's minimap draws no road map under such a project.
Improved
- A scan too large for this server is refused at once, with the figures, instead of running for minutes and failing. E57 files are now checked the way LAS files are, and so is building the whole-site merged cloud.
- If the server does run out of memory part-way through a conversion, the scan now says so in plain words. The upload is kept and nothing already on the server changes.
- A unified E57 (one merged cloud, or a mobile-scanner capture) no longer shows a scan station; scans captured from a tripod still do. Existing projects keep all their data: only that station marker is hidden. Panoramas imported for such a cloud are stations of their own.
- A section box you have set stays where it is when you click on the cloud.
- Touch rotate and pan are about 15% less sensitive.
- The maps credit their data: OpenStreetMap and Natural Earth.
Fixed
- An upload too large for the server's disk is refused with "Not enough disk space" instead of "There was an error parsing the body", and nothing is written.
- IFC windows are drawn at their true size: openings and clearance zones are no longer drawn as part of the window.
- The Delete project dialog says what deleting does: the project moves to the recycle area, can be restored for 14 days, and is then permanently deleted. It no longer says that nothing is deleted.
Data compatibility
- Existing project data opens unchanged. On each start Cairn reads any E57 scan it has not yet classified and records, in that project's own record, whether it is a unified cloud; nothing else in a project is rewritten. A scan it cannot read, such as one whose original file has been deleted, keeps its station.
- Rolling back to the previous version still reads the data. Unified E57 scans converted before this release show their station again.
0.3.0-pilot.16 3 October 2026 Security-critical
Before you upgrade
- After this upgrade the installation serves nothing to anyone until an Administrator signs in and renews the installation acknowledgements once. Every page, every share link and every viewer stays closed until then, for every account. Plan to sign in as an Administrator straight after the upgrade. An installation without accounts shows the acknowledgements on its sign-in page instead, for the operator to record.
Security
- The installation acknowledgements are required in every mode, and each record keeps what was agreed. An installation running without accounts could be used without anyone ever accepting them. A record now holds the wording that was shown, who accepted it and when; any change to that wording asks for one renewal, and the record it replaces is kept.
- Each action a client account may not take is refused by a rule of its own. Seven upload, import and conversion actions relied on one shared check. Each now carries its own, so no single check stands alone in front of them.
Changed
- A surveyor can stop a conversion, as an administrator can.
- First-run setup asks for the Administrator's own name and will not record a blank one.
Data compatibility
- Existing project data opens unchanged; nothing in a project is rewritten.
- The account store keeps the renewed acknowledgement record and, beside it, the one it replaced.
- Rolling back to the previous version still reads the data and the account store, and stops asking for the acknowledgements.
0.3.0-pilot.15 28 September 2026 Security-critical
Security
- A share-link holder can no longer read files the viewer never shows. Adding certain characters to an address let anyone holding a share link, and any signed-in account, fetch a project's private files, including its raw scans, exports and the record of its share links, and do the same for other projects on the server. Cairn now decides who may see a file using exactly the address it serves, so the two can no longer differ.
- A password-protected share link now needs its password. Holding the link alone could be enough to open it. A browser now has to prove it was given the password, and changing or removing a link's password takes effect on the next request.
Fixed
- Protecting a link with a password is a choice you make, not a filled-in field. The share dialog has its own "Require a password" tick box, separate from "Allow snapshots". A password a browser fills in by itself no longer protects a link by accident.
Improved
- Files the viewer loads are checked for access faster.
Upgrade notes
- Anyone who has already opened a password-protected share link is asked for the password once more, the first time after the upgrade.
Data compatibility
- Existing project data opens unchanged; nothing is rewritten.
- Rolling back to the previous version still reads the data, and brings back both security flaws this release closes.
0.3.0-pilot.14 28 September 2026
Improved
- Station View shows a picture almost at once. A small preview of the station photograph appears first, usually in under half a second, and the full photograph takes its place as soon as it arrives. The full photograph is now asked for as soon as the preview starts arriving, so it is not held up behind it.
- Walking to the next or previous station is faster. While you look around a station, the points around the stations either side of it load in the background, so their full detail is usually ready before the walk ends.
- Station View shows the photograph before the points, and walks to stations up to 30 m away rather than jumping.
- A project's first points arrive sooner when it opens.
- Files behind a sign-in or a share link are checked for access faster, which helps when several people view at once.
Fixed
- Files that need a sign-in or a share link are marked private and are checked again each time, so a browser never shows a stale copy of a re-converted scan.
- A software library Cairn's server uses (anyio) is updated to 4.14.2.
Upgrade notes
- On its first start after the upgrade, Cairn makes a small preview of each station photograph and keeps it inside that project's folder. This takes a few minutes on a large project; the full photographs are shown as before while it runs. No action is needed.
Data compatibility
- Existing project data opens unchanged; nothing existing is rewritten.
- Rolling back to the previous version still reads the data; the previews are ignored by it.
0.3.0-pilot.13 15 September 2026
Fixed
- A point cloud no longer draws solid black on a device whose graphics driver cannot run the high-quality view. Cairn used to decide which rendering path to use from the graphics adapter's reported name; a device reporting a name Cairn didn't recognise was opened in the high-quality path regardless, and on hardware that path's driver support is actually missing, nothing drew. Cairn now checks what the driver can actually do and opens those devices in the faster, lower-detail path instead, with an on-screen note explaining why.
Upgrade notes
- If a device previously showed a black point cloud, it should now render normally in the faster view, with a one-line note saying why that view was chosen. No configuration or action is needed.
Data compatibility
- Existing project data opens unchanged.
- No on-disk format is rewritten.
- Rolling back to the previous version still reads the data.
0.3.0-pilot.12 15 September 2026 Security-critical
New
- Put a project on the map. A surveyor can set where a project sits by clicking the map or by searching for an address, and the pin is stored with the project as a position somebody chose rather than one Cairn guessed. Address lookup is optional and the firm nominates the service it uses; no provider is built in.
- The office server can be upgraded. Until now only the single-workstation shape had an upgrade path. The Linux server has one, and it backs up and verifies that backup before it replaces anything.
- Cairn can tell you why it was slow or why it stopped. Timings, crash context and browser-side errors are recorded, and the diagnostics bundle carries them. Nothing leaves the server unless an operator produces a bundle and sends it.
- A one-page emergency sheet ships with the package. BREAK-GLASS.md is the page to hold when Cairn is not answering: what to check and in what order, how to restart safely, and what must never be invented. The full runbook is still there and still complete.
- How much work Cairn will do at once can be set. Two settings cap how many conversions run together and how many jobs run at all, so a smaller server can be told to do one heavy upload at a time. The defaults are unchanged; a server that sets neither behaves exactly as before.
- A release that carries a security fix now says so everywhere. The marking reaches the release notes, the package and what the upgrade prints, on both Windows and Linux. An ordinary release deliberately says nothing, so the warning stays worth reading.
Fixed
- A client can install from the runbook alone. A package built from a clean checkout could stop partway through and tell the operator to use the supplied package unedited — which they had. The cause was a line-ending difference in one file that never reached the operator's hands at all.
- A backup can be restored into an installation that is already running.
- Cairn refuses to start rather than answer on an address it cannot serve. A configuration that could not work now stops at startup and says which setting is wrong, instead of starting and returning empty pages.
- Errors say what actually happened. Being signed out, not being allowed, the server being busy and the server being unreachable are four different messages. Previously all four could read as "Server offline", which sent operators to look at a machine that was fine.
- Projects open faster under load. Two changes — a directory scan that ran on every request, and an extra layer wrapped around every request — together remove about a third of the response time when many people are viewing at once.
- A station keeps working after its scan is deleted.
- Annotations made offline no longer report themselves saved before they have been.
- On a phone, the top bar no longer overflows, the landscape controls no longer overlap, and the map can be edited.
- The minimap falls back to the server's project position when it has nothing better.
Security
- A restart no longer clears a lockout. Failed sign-in counts, request throttles and share-password attempts lived in memory, so restarting Cairn handed every caller a fresh set of attempts. They are now kept on disk and survive a restart.
- Private files are no longer inside the directory Cairn serves from. They were protected by a rule rather than by where they sat; they now sit somewhere that is not served at all.
- A backup archive cannot be used to mint a session. The session signing key is now kept encrypted under the host's protected store rather than regenerated, so signing in survives a restart — and a copy of the data on its own still grants nobody access.
- A share's password hash no longer leaves the server.
- Requesting a password reset is no longer an unlimited anonymous write.
- A temporary administrator password grants nothing an ordinary one would not.
- The page policy no longer permits inline styling, closing a route that could be used to alter what a page appears to say.
Upgrade notes
- READ THIS IF YOUR SERVER SIGNS IN WITH A SHARED TOKEN. The single shared access token is no longer a way in. It was one secret held by everyone who had it, with no identity behind it, and named accounts replace it entirely. A server configured with a shared token has no accounts yet — that setting prevented them being created — so after this upgrade it opens on the first-run screen and asks for a first administrator. If that is your server, plan who creates that account before you upgrade, not after.
- Cairn comes back locked after any restart, including this upgrade, and has to be unlocked. That is how it is meant to work: the key is held only in memory. The upgrade does this for you and tells you if it could not.
- The upgrade backs up your data and checks the backup before it replaces anything. If the backup does not verify, the upgrade stops and nothing is changed.
Data compatibility
- Projects, scans, panoramas, models, annotations and shares are carried forward unchanged. No conversion runs and nothing is rewritten.
- Going back to an earlier version means restoring the backup taken during this upgrade. Once this version has written data, reinstalling an older image is not a way back.
0.3.0-pilot.11 2 September 2026 Security-critical
New
- Office-server installation. Cairn can now be installed on a machine the firm owns or rents and reached at the firm's own domain, with a public certificate obtained and renewed automatically. The single-workstation installation is unchanged.
- An operator can reset a locked-out administrator from the server. No email and no second administrator is needed. Cairn generates the temporary password and prints it once; it cannot be typed on the command line, so it never lands in shell history.
Fixed
- The detailed map no longer stalls while it is being panned, and the note about it now sits under the map instead of over it.
- A LAS or LAZ file's declared quantisation is read, checked and recorded with the Project, and is never silently made coarser during conversion. Where the source is coarse enough to limit what a Measurement can support, Cairn records that too.
Security
- The sign-in page no longer discloses the password rules to a visitor who has not signed in.
Upgrade notes
- A single shared access token is no longer a way in, and a server that used one will ask for a first administrator. Cairn signs in with named accounts, so that everything a person does is attributable to them. The shared token was never a supported way to run Cairn and has now been removed. A server configured with one has no accounts yet — that setting prevented them being created — so after this upgrade it opens on the first-run screen and asks for an administrator. Create it, then add an account for each person who needs one. This is expected, the sign-in page explains it on the day, and the server is not left unprotected at any point: it asks who you are before and after. Existing Share links are unaffected. The CAIRN_TOKEN setting is now ignored and can be removed.
- The installation shape is chosen once. Workstation or office server is decided when Cairn is first installed and is recorded. Re-running the installer never converts one into the other, because that would move the address every Share link already sent points at.
- An office-server installation needs its DNS record in place before the install runs. The installer checks for it first and stops if it is missing.
Data compatibility
- Existing Project data opens unchanged.
- No on-disk format is rewritten. Newly converted Scans record the source quantisation as extra fields alongside what is already there.
- Rolling back to the previous version still reads the data: nothing existing changed shape, and Cairn ignores a field it does not recognise.
0.3.0-pilot.10 1 September 2026 Security-critical
New
- A System Health area in the dashboard, and a notice that stays on screen until an operator dismisses it when something needs attention. An administrator can also read the installation's log state without opening a shell on the server.
- The clean-up that actually reclaims disk now runs for the life of the process — once at start-up and once a day after that — instead of only when Cairn starts. A long-running server no longer has to be restarted to get space back.
Fixed
- A Project holding only LAS files whose coordinate frames disagree no longer hides the mismatch; the warning is shown.
- The number of decimal places a Measurement shows now comes from what the underlying data can actually support, rather than from a fixed setting.
Security
- After an upgrade to the three-role model, an installation now requires an operator to state, once, what each existing account is. No account silently keeps administrator authority, and none is silently demoted.
Upgrade notes
- This is the release that requires the role assignment, and it happens once. The symptom is that nobody can sign in and the sign-in page says the account has no role. That is expected, not a fault: an installation created before the three roles existed does not record which of them its accounts were meant to be, and Cairn will not guess. The assignment is done from the server, because while the installation is in this state there is no dashboard to open. The runbook's section Assign a role to every account after upgrading to the three-role model is the whole procedure.
- The recovery window for data deleted inside a Project is now seven complete days, not fourteen. Eligibility is worked out from the age of the files, so the shorter window applies to what is already staged: anything removed more than seven days ago becomes eligible at the very next daily sweep. Reclaiming cannot be undone. If anything staged in the past fortnight might still be wanted, restore it before upgrading. The fourteen-day window for a whole deleted Project is separate and is unchanged.
Data compatibility
- Existing Project data opens unchanged. What this release changes is the account store and when staged data is reclaimed.
- Nothing inside a Project is rewritten. The account store gains a record of which role model it was written under, and every account's role becomes explicit rather than assumed.
- Rolling back to the previous version: Not assessed for the account store. No rollback across the role assignment has been performed. Project data is untouched by this release.
0.3.0-pilot.9 31 August 2026 Security-critical
New
- The Surveyor role. An Administrator can create an account and assign it. A Surveyor uploads, imports, checks the work, renames a Project, removes data inside one and creates or revokes Share links — and cannot delete a whole Project, purge, manage people or touch the encryption key.
- Panorama orientation, set in the browser. A Surveyor can align a Panorama onto the point cloud: one setting for the whole Project, with an override for any station that disagrees. It moves the Panorama, never the survey data, and everyone who can enter Station View sees the saved result.
- A Surveyor can rename a Project's displayed name without changing its identifier and without breaking a Share link that has already been sent.
- A Surveyor can remove a Project's Model.
Fixed
- Measuring in Station View uses the point cloud only. Where there is no usable point behind the image, Cairn shows an error instead of a number.
- Height refuses a pick that is not a real value, and the measurement panel now follows the Measurement being placed rather than staying where it started.
- An OBJ file is checked by its content rather than by its name.
Security
- Every denial of data removal inside a Project is enforced by a rule of its own on the server, rather than depending on the order in which one layer runs before another.
- The controls for removing a Scan, a Panorama or a Model are never built for a Share link holder.
Upgrade notes
- The Surveyor role exists from this release, but existing accounts are not touched by it here. The step that requires an explicit role for every existing account arrives in the next release.
Data compatibility
- Existing Project data opens unchanged.
- A Project's description gains optional fields for the Panorama orientation. Nothing existing is rewritten.
- Rolling back to the previous version still reads the data: Cairn ignores fields it does not recognise.
0.3.0-pilot.8 28 August 2026 Security-critical
Fixed
- The package archive records file permissions correctly and spells its manifest paths consistently, so a package unpacks the same way on Windows and on Linux.
Security
- Exporting Measurements as a CSV is denied to Client accounts and to Share link holders — the control is not built for them, and the action is refused as well, so putting the control back by hand achieves nothing.
Data compatibility
- Existing Project data opens unchanged.
- No on-disk format is rewritten.
- Rolling back to the previous version still reads the data.
0.3.0-pilot.7 25 August 2026 Security-critical
New
- The encryption key is no longer kept in plain text in configuration. It is wrapped, and the secret that opens it is supplied by the host computer each time Cairn starts — on Windows through a user-scoped platform secret store, on supported Linux through a systemd encrypted credential. A copy of Cairn's data and configuration alone is no longer enough to recover the key.
- Key rotation from the dashboard, by a named Administrator. The old key is kept until every Project has been re-wrapped and verified, the new recovery value is shown for the operator to store externally, and an interrupted rotation is resumed rather than restarted.
Fixed
- The packaged Linux installation now installs, and each package records the exact source revision its image was built from.
Upgrade notes
- Read this one before upgrading. This is the first protected-key upgrade. Cairn detects the retired plain-text key before any outage and asks the operator to confirm the existing external recovery copy. It then imports the old value into host protection, removes the plain-text line from configuration and replaces it with a freshly generated key.
- Keep the old recovery copy until Cairn has verified every new wrap and you have stored and confirmed the newly displayed recovery key. The new key belongs outside the machine, in your organisation's approved password or secrets system. Nobody else holds a copy, and it cannot be recovered from Cairn's own data.
- Afterwards, if the host cannot supply the unlock secret — a different Windows user, a rebuilt machine — Cairn stays locked rather than inventing a replacement, and recovery uses the externally held value.
Data compatibility
- Existing Project data opens unchanged when the upgrade is run as described above.
- Yes, something is rewritten. The plain-text key is retired from configuration and every Project's key is re-wrapped under a newly generated installation key. That step is not designed to be reversed.
- Rolling back to the previous version: Not assessed. No rollback across this step has been performed. If you have to go back, restore from the backup the upgrade takes at the start.
0.3.0-pilot.6 25 August 2026
New
- The optional detailed map is drawn with a map library bundled into the package rather than by Cairn's own drawing code, which handles a full street-level map properly. Nothing is downloaded: the map is still a file installed on your own server.
Upgrade notes
- Superseded the same day by the release above. Go to that one instead.
Data compatibility
- Existing Project data opens unchanged.
- No on-disk format is rewritten.
- Rolling back to the previous version still reads the data.
0.3.0-pilot.5 24 August 2026
New
- The running version is now visible from inside the installation — in the sign-in page footer and on the dashboard — and it is read from the server rather than typed into a page, so it cannot go stale.
Fixed
- The map behind the Project pins draws faster while it is being moved.
- Zooming out is bounded by what the installed map actually covers, so the view no longer runs off into blank space.
Data compatibility
- Existing Project data opens unchanged.
- No on-disk format is rewritten.
- Rolling back to the previous version still reads the data.
0.3.0-pilot.4 23 August 2026
New
- An optional detailed map, with street-level detail, installed by putting one file into the data folder. There is no setting to change and nothing to restart, and the guide that explains it now ships with the package. Cairn never downloads a map; the built-in outline map continues to work without it.
Upgrade notes
- The detailed map lives in your data folder rather than inside the program, so upgrading replaces the program and leaves the map alone. It is deliberately left out of backups, because it is large and can simply be reinstalled — so reinstall it after rebuilding a server from a backup.
- Superseded the next day by the release above.
Data compatibility
- Existing Project data opens unchanged.
- No on-disk format is rewritten. The map is a new optional file in the data folder.
- Rolling back to the previous version still reads the data.
0.3.0-pilot.3 23 August 2026 Security-critical
Security
- Cairn signs every backup archive it writes. A checksum only shows that a file is undamaged — anyone who can rewrite an archive rewrites the checksum beside it in the same breath. The signature shows the archive is the one your Cairn produced, and not something put there afterwards. The verifying half is a public fingerprint you can copy freely; the signing half never leaves the machine and is never written into a backup or a diagnostic bundle.
Upgrade notes
- Archives written before this release can never be signed retrospectively. They are still good backups and will still restore; Cairn reports them as integrity-checked but not authenticated, and a restore drill against one needs the documented flag that says so on screen. Everything written after the upgrade is signed.
- The backup taken at the start of an upgrade is written by the version you are leaving, so upgrading onto this release produces one last unsigned archive. That is expected.
- Record the backup fingerprint the installer prints, in more than one place. The day you need it is the day the machine no longer exists.
- Superseded the same day by the release above.
Data compatibility
- Existing Project data opens unchanged.
- No on-disk format is rewritten.
- Rolling back to the previous version still reads the data.
0.3.0-pilot.2 23 August 2026 Security-critical
A fortnight of work on the boundary between what an audience may reach and what it may not. It is the largest security release so far.
Security
- A Project's original Scans and exports are denied to every caller, including an administrator, by a single rule that reads the file the server is about to open rather than the address as typed. Alternative spellings of the same address no longer reach a different answer.
- A Share link holder is scoped to the Project the link authorises. A crafted address could previously reach another Project's streamed data.
- The internal directories that sit beside the Projects — the account store, the deleted-Project area and staged copies of replaced data — are denied by resolved path.
- The raw Project description is refused off the static file mount in every mode. It carries every Share link token and password for that Project.
- The wrapped Project encryption key is never returned over the interface.
- Creating, supplying or rotating the encryption key requires a named, signed-in Administrator, and a stored key Cairn has never seen is never silently overwritten.
- Guessing a Share link's password is bounded by an admission control of its own, so a whole office opening a legitimate link is not throttled while guessing still is.
- The dashboard map no longer discloses a site's location to a third party. It is drawn from a map on your own server, and no request leaves the installation to draw it.
- Restoring a backup is an offline operation, enforced by the operating system rather than by convention, and an archive containing link members is refused rather than unpacked.
New
- A running conversion can be stopped from the dashboard.
- Panoramas can be removed and re-imported without affecting the point cloud.
Fixed
- A LAS file whose contents are shorter than its own header claims is refused rather than converted.
- An encrypted upload is made durable before it is published under the Scan's name, so an interrupted write cannot replace readable data with an unreadable file.
Upgrade notes
- Superseded the same day by the two releases above. Go to the newest instead.
Data compatibility
- Existing Project data opens unchanged: Not assessed. This release spans a fortnight and touches storage, the account store and the encryption code, and no upgrade from the release before it was performed.
- No file format change was found; the encryption change is about making a write durable rather than about the format.
- Rolling back to the previous version: Not assessed, for the same reason.
0.3.0-pilot.1 9 August 2026
The first package assembled for the operational pilot: the image, the installer and the operator scripts, supplied as one folder to copy onto a machine.
What Cairn was at that point
- LAS, LAZ and E57 Scans converted for viewing in a browser, with IFC, DXF and LandXML Models and Panoramas imported alongside them.
- Navigation, Station View, section boxes, Annotations, saved views and Measurement, on a desktop or a phone.
- Share links: one Project, anonymous, any expiry from none up to a year with thirty days the default, an optional password stored salted and hashed, and revocable at any time.
- Accounts with passwords hashed using scrypt and a unique salt, in two roles — administrator and client account — with per-Project access for the latter. The Surveyor role came later.
- Encryption at rest for original Scans, chosen per Project.
- Local usage logs kept for ninety days, an enforced browser content policy, refusal of uploads when the disk is nearly full, and the backup and restore-test scripts.
Data compatibility
- Not applicable: this is the first package, and there was nothing to upgrade from.