this post was submitted on 10 Sep 2025
25 points (100.0% liked)

Selfhosted

51445 readers
425 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Is anyone here running Sandstorm? If yes, what's your experience?

I really like the idea of "grains" where an instance of the app runs for each document/project/unit of data your app has. It does improve security a lot, because it is very similar as running root-less docker.

I also like the unified auth and user management sandstorm provides.

you are viewing a single comment's thread
view the rest of the comments
[–] HelloRoot@lemy.lol 3 points 5 days ago* (last edited 5 days ago) (1 children)

I don't get that part. Can you explain it please?

Dokploy has a list of hundreds of "templates" where you basically one click install a working docker container with said app. But there is no deeper integration.

Is sandstorm different somehow?

[–] verstra@programming.dev 2 points 4 days ago

For example, ether pad (document editor) is a) packaged to be single-click deployable on sandstorm (this is similar to dokploy), but also b) modified so that it runs each document as a "grain".

In sandstorm, "grain" is some chunk of data + an instance of the app running. So when you open a document, it will spawn a new process for it on the server and attach the data needed to that process (similar to how you would attach volumes to docker containers). This grain is isolated from other open documents, which is good for security, but also good for development:

  • apps don't need to handle the organization or storage of documents (they just write to a dir and sandstorm associates it with the grain),
  • apps don't need to handle user auth or permissions,