19 October 2026

Compass 0.6.0: A map that stays fast as your account grows

The map moves from DynamoDB to a SQLite file and keeps its history. On a 100,000-resource account, writing the map after a scan takes seconds instead of the better part of an hour, and the map opens in under a second.

Fast at 100,000 resources

On a synthetic account of 100,000 resources and 260,000 relationships, writing the map after a scan takes 13 seconds, where the old store took 18 minutes, and the map's first load takes under a second. On 10,000 resources, coverage and ownership answers that took 20 seconds take under one.

The map is one file

Each workspace's map is a SQLite file on a new map-data volume. The daemon writes a scan in one transaction while the dashboard keeps reading, so you never see half a scan. DynamoDB keeps the jobs, decoys and pull requests.

/compass/data/map/<workspace>.sqlite

Nothing is deleted

A scan no longer erases what it did not find: it marks it gone, with the time it appeared and the time it went. Reading the map as it was and comparing two scans build on this in a later release.

Your map moves over on its own

The first start after the update copies your existing map into the file, once, and leaves the DynamoDB table as it was. To go back, set COMPASS_MAP_STORE=dynamodb in .env and restart.

COMPASS_MAP_STORE=dynamodb

Back up the map

One command copies the map while Compass runs; restore it by putting the copy back with the stack stopped.

compass mapper backup out=/compass/map/map-backup.sqlite

After the update

Compass is open source (Apache-2.0).

Code, changelog and issues: github.com/beamreach-ai/compass. Already running it? The update card on Settings → Updates shows these notes before you update.