Roadmap
Where it is going, and why.
Data alone is not enough. Every step on this list should turn point clouds, photos and measurements into something you can check and pass on: a finding, a report, a decision. The order changes when we learn something better. When it does, this page says when and why.
- Released
- siteBits 0.10.3
- Next version
- 0.11 · preview
- As of
- 21.10.2026
Stages
-
done · 0.10.3
View, measure, discuss
Point clouds, panoramas, photos and meshes in the browser; distance, height and area with a note on what the measurement rests on; findings with a thread; roles, invitations and read-only links; REST API and MCP server; checked and signed releases.
Why The shared ground has to hold first: everyone sees the same scan and talks about the same spot.
-
in progress · 0.11
Sun and display
Display modes for meshes (texture, grey, normals, wireframe), sun position with shadows for any date and time, a shading and yield report for roof areas, a sunlight report for gardens. Preview, the interface may still change.
Why A model becomes an answered question, even without a large building project: how much sun does this surface really get?
-
in progress · 0.11
Checks and reports
Check a delivery against a catalogue of requirements: reference system, formats, checksums, point density, gaps, ground resolution and control points. For each requirement “met”, “not met” or “cannot be checked”, with reason and evidence. Preview, command line first.
Why Clients have to accept survey data and rarely have an open tool for it. The same catalogue lets service providers check before they deliver: one yardstick for both sides.
-
planned
Upload in the browser
Upload point clouds, meshes and photo exports in the browser; the server prepares them with the same checks as the command line does today.
Why The front door without a command line, for everyone who has data but does not want to look after a server.
-
planned
From photos to a model
Open photogrammetry as a connected service: upload drone photos, get a point cloud and mesh back, checked like any other import.
Why The whole chain from capture to report should work without expensive licences.
-
planned
Large models at full resolution
Meshes and panoramas in tiles with levels of detail, so even very large models load smoothly at full texture resolution.
Why When you zoom in close, you should see what was captured, not a scaled-down copy.
-
planned
Share and guide
Embed views, tours with annotations, preview images.
Why Results should arrive where people already read: on your own website or in the report.
-
planned
Take part
Email notifications, attachments on findings, blurring of people and number plates in photos.
Why The more people work on a project, the more feedback and privacy matter.
-
planned
Measure over time
More measurement types and profile sections, export as DXF and GeoJSON, several captures of one object side by side.
Why Buildings change. Only comparing two points in time shows what happened.
-
planned · 1.0
1.0: a promise to others
Stable interfaces and package format within 1.x, proven in real use over weeks, reporting and operation settled so that schools and public bodies can approve it.
Why 1.0 does not mean “everything is done” but “you can build on this”. There is no date; the criteria decide.
-
planned · 1.1
Heritage and universities
Mapping areas with a legend, observations next to defects, archive packages that stay readable without siteBits, sign-in with university accounts, full accessibility.
Why Buildings should stay documented and readable for decades. Every building block already plans for it.
Deliberately not
- No public hosting platform
- siteBits runs as your own instance, on your premises or operated by us. Your data does not sit in a shared pool.
- No capture app of its own
- Capture with the device you already have. siteBits accepts the exports.
- No modelling as a service
- Drawing plans from scans is manual work and well served. siteBits delivers the data for it and checks it.
- No accuracy without evidence
- Without control points or check distances it says “model measurement, not verified”, and never a ± value.
What changed
Changes of course, with date and reason, so you can follow why the list above looks the way it does.
21 Oct 2026
New: checks and reports, placed before upload.
Looking at tenders showed that there are hardly any open tools for clients to check a delivery against their requirements. The report part from “sun” could be reused for it directly.
21 Oct 2026
New: sun and display, brought forward.
A sunlight and shading report is useful even with a small dataset, for roofs, gardens and planning, and does not have to wait for a large project.
20 Oct 2026
Broader scope.
Besides construction also heritage, universities and cultural heritage. Upload and processing in the browser move forward; own instances instead of a public platform.
19 Oct 2026
First public version 0.10.3.
Source code on GitHub under EUPL-1.2.
Something missing, or would you weigh things differently? Write to hallo@sitebits.de or open an issue on GitHub. What changed in each version