the solstone app takes in what you share with it, and it all goes into your journal: an open source, local-first memory the agents you use can work from. on your devices, always private, only yours.
solstone is a personal journal platform, all yours, in two parts you own: the solstone app and your journal, the memory. from your journal emerge a knowledge graph of every person and project in your life and full-text search across your whole life. you stop managing your memory and start being present. your journal is always private, only yours.
open source and self-hostable, with optional services operated by sol pbc.
looking for the journal's code? it moved to solstone-journal. this repo is now the family index and the home of solstone's platform release metadata and installer rail.
| repo | what it is |
|---|---|
| solstone-journal | the journal that holds and keeps your memories. |
| solstone-macos | the solstone macos app. |
| solstone-linux | the linux desktop app. |
| solstone-windows | the windows app. |
| solstone-android | the android app. |
| solstone-swift | the ios app. |
| solstone-tmux | solstone for tmux. |
this repository generates, validates, signs, and publishes the platform-level platform.json release metadata manifest, manages the atomic latest pointer across release lanes, and provides the POSIX platform installer build rail (install.sh.in -> install.sh).
for linux and macos installation and verification, plus linux recovery, read INSTALL.md.
save the canonical installer and inspect its options:
curl -fsSL https://solstone.app/install.sh -o install.sh
sh install.sh --helpcheck that the download succeeded before running the script. https://solstone.app/platform-install.sh remains a byte-identical compatibility URL. on macos, this installer acquires the native apps; it never installs a standalone journal runtime.
terminal is part of the solstone app, is turned on in it, and needs tmux on the computer. an owner who already has solstone for tmux moves it with solstone update. when only solstone for tmux is installed, the direct upgrade is curl -fsSL https://solstone.app/install.sh | sh -s -- --upgrade --components tmux.
for authoritative definitions, refer to:
- native component pins:
pins/ - current installer revision:
compat/installer_revision - minimum installer revision floor:
compat/minimum_installer_revision - component handler contracts:
contracts/ - target architecture and package mappings:
src/solstone_platform/targets.py
for terminal copy and local previews, see installer strings.
# Build (compile Python sources)
make build
# Build the production POSIX platform installer from the checked-in public pin
make build-installer
# Run unit and regression test suite
make test
# Lint source files and check headers
make lint
# Verify formatting and encoding
make format
# Run full hermetic CI gate (offline, non-root)
make ci
# Run CLI directly
PYTHONPATH=src python3 -m solstone_platform.cli --helpschema-2 catalogues use the selected journal version and a positive catalogue
revision. journal 2.0.33 with revision 1 is published at 2.0.33-r1.
a desktop release can advance the revision while keeping that journal
version and its payloads. a new journal version normally starts at revision 1.
historical schema-1 catalogues keep their original bare coordinates.
deploy installer revision 8 before promoting the first revised catalogue.
that reader supports both formats; after promotion, keep a capable reader at
both installer URLs. native component and package versions keep their existing
formats without a catalogue suffix.
when a published linux component should become the platform default, prepare the
new catalogue directly from its signed release. the
preparation path validates the downloaded
artifacts, requires every unselected component entry to remain exact, and records
the latest version and ETag that publication is allowed to replace.
a desktop release adds its aarch64 set when it publishes
solstone-linux-<version>-linux-aarch64.rust-release-manifest.json beside the
x86_64 one. a recut that would drop an architecture the current catalogue
carries is refused. deploy installer revision 16 before promoting the first
catalogue that lists desktop aarch64.
deploy installer revision 17 before promoting the first catalogue whose
journal no longer ships a journal command; earlier revisions look for it to
run journal setup and uninstall.
export SOLSTONE_R2_ENDPOINT="https://<account>.r2.cloudflarestorage.com"
export SOLSTONE_R2_BUCKET="<bucket>"
export AWS_ACCESS_KEY_ID="<access-key-id>"
export AWS_SECRET_ACCESS_KEY="<secret-access-key>"
PYTHONPATH=src python3 -m solstone_platform.cli prepare-recut \
--version 2.0.33-r1 \
--replace journal=2.0.33 \
--out /var/tmp/solstone-release/platform-2.0.33-r1inspect platform.json and recut-receipt.json, and compare the candidate's
components object with the signed base named in the receipt before signing.
signing remains a separate, explicit production step. retain the prepared files,
receipt and detached signature before publication so an interrupted attempt can
retry those exact bytes. publish the
signed candidate with its receipt:
SOLSTONE_PLATFORM_PRODUCTION=ack PYTHONPATH=src python3 -m solstone_platform.cli publish \
--manifest /var/tmp/solstone-release/platform-2.0.33-r1/platform.json \
--signature /var/tmp/solstone-release/platform-2.0.33-r1/platform.json.minisig \
--journal-dir /var/tmp/solstone-release/platform-2.0.33-r1/journal \
--desktop-dir /var/tmp/solstone-release/platform-2.0.33-r1/desktop \
--bootstrap-file /var/tmp/solstone-release/platform-2.0.33-r1/bootstrap/solstone-journal-2.0.33-install.sh \
--expected-latest-receipt /var/tmp/solstone-release/platform-2.0.33-r1/recut-receipt.json \
--acknowledge-productionif latest changed to a different release after preparation, publication
refuses without adopting the new base. prepare a new candidate from the current
release instead. on a retry, the
publisher reuses an immutable object only
when its bytes and metadata match, and uses at most one conditional write to
advance latest. if an abandoned attempt has claimed a coordinate, select a
higher revision for the same genuine component update. preparation requires a
strictly newer selected component; changing only catalogue metadata is refused.
make ci also runs the offline catalogue qualification. to run it alone:
make qualifysolstone is built by sol pbc, a public benefit corporation. the benefit purpose and the data covenants are written into our articles of incorporation, not a privacy policy: your data is never sold, licensed, or used for anything but serving you. they can't be amended without the founder's personal signature, and after him the language can only get stronger, never weaker. or skip the trust question entirely and run it yourself.
product site · company · bluesky @solstone.app
See changes for installer updates.