https://github.com/sandstorm-io/sandstorm
Looks pretty active.
In We Need More Alternatives to Facebooksandstorm-io
sandstorm
JavaScript2014–2026
sandstorm-io / sandstorm
sandstorm
Sandstorm is a self-hostable web productivity suite. It's implemented as a security-hardened web app package manager.
21Distinct people
53Mentions
0Explicit recommenders
7.1KGitHub stars
What to know before exploring
What it is
Sandstorm is a self-hostable web productivity suite. It's implemented as a security-hardened web app package manager.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 9:01:12 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year53 dated mentions
Observed mentions: 2014-06-29 18:44:23 UTC to 2026-09-06 13:44:51 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 11 | 0 | 11 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 12 | 0 | 12 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 10 | 0 | 10 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 5 | 1 | 4 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
Sandstorm
Sandstorm is a self-hostable web productivity suite. It's implemented as a security-hardened web app package manager. Sandstorm makes it easy to run your own server.
Use Sandstorm to install apps to create documents,
spreadsheets, blogs,
git repos, task lists, and
more as easily as you'd install apps on your
phone.
Sandstorm is open source and can be installed on any x86-64 Linux
system.
Read more at: https://sandstorm.io/
Try the demo: https://demo.sandstorm.io/
Documentation available at: https://docs.sandstorm.io/
Installing
See installation instructions in the Sandstorm documentation.
Using Sandstorm
See the overview in the Sandstorm documentation.
How It Works
See how it works and security practices in the Sandstorm documentation.
How to Package Apps
See the developer hub in the Sandstorm documentation.
Contribute
Want to help? Check out CONTRIBUTING.md. Also see our community page or get on our discussion group and let us know!
Read the full README on GitHubWhat Hacker News says
5 sourcesSandstorm.io – easter egg in source code
4 points · Open discussionYes. You can click the "download backup" button in the top bar when you have a grain open to download a zip file of all its contents. You can then upload that to any other server to restore the grain there.
Currently there is not a mass-download or mass-transfer feature; you have to do each grain one at a time. But you probably won't generate that many grains if you're just testing it out, so it ought to be OK. We plan to add mass-transfer in the future.
See also: https://github.com/sandstorm-io/sandstorm/tree/master/roadma...
In Sandstorm is returning to its community rootsThat was a restriction very early on, but we've supported e-mail login for a long time. And as of today, LDAP and SAML login are now available in the base project as well (used to be paid features), so you can run a local LDAP server or SimpleSamlPhp for self-contained login.
See also: https://github.com/sandstorm-io/sandstorm/tree/master/roadma...
In Sandstorm is returning to its community rootsThanks for the feedback!
1. We know the UI needs work and have plans to improve it. We are very aware that webkeys are not user-friendly; they were always meant as a stopgap measure while we build better UI. Some things about mobile here: https://github.com/sandstorm-io/sandstorm/tree/master/roadma...
2. The amount of work an app port requires varies a lot depending on the type of app. Self-contained apps that don't talk to the outside world can often be ported in a few minutes. But, indeed, some apps need work to integrate with the appropriate Sandstorm APIs. We've been working to make this easier by, for example, setting up an HTTP proxy inside the app which can make communicating with external OAuth services mostly transparent, while still respecting the Sandstorm permission model. With better tools we think we can automate most things
Read the rest
, we just haven't gotten there yet.
3. There are multiple Sandstorm apps which let you post e.g. blogs with no Sandstorm UI frame around it. We have some features in-progress which extend this to more apps. But note that part of the goal of Sandstorm is to generalize a lot of the UI such that apps don't have to repeatedly build the same things, like login, access control, notifications, etc. We need to hang that UI somewhere, hence the need for that frame. But we have ideas that will make it look a lot more like an integrated part of the app UI in the future.
4. We dogfood a lot. We write design docs in Etherpad, manage tasks in Wekan, etc. Our github, google groups, and IRC existed before Sandstorm was functional. The main reason we haven't switched over is because switching is costly and it seems like there are better things we could do with our time.