A new deployment mechanism for Trilium: standalone mode #9733
Replies: 5 comments 6 replies
-
|
cc. @perfectra1n , @Nriver , @FliegendeWurst |
Beta Was this translation helpful? Give feedback.
-
|
Looks really nice @eliandoran A tiny thing i noticed is that when i 'Logout' of the standalone instance I get a not-so-nice toast. |
Beta Was this translation helpful? Give feedback.
-
|
Is this safe to test with a self-hosted server? |
Beta Was this translation helpful? Give feedback.
-
|
Quite interesting idea. I have zero knowledge for PWA and WASM, it looks like magic to me : ) Find a little glitch here, the language selection does not work on android browser apps. 1.mp4I can choose Chinese language on PC in this page, but doesn't seem to take effect, it still loads English. |
Beta Was this translation helpful? Give feedback.
-
@eliandoran
Looks like these won't be needed in the future. You can import directly from "@triliumnext/core" and remove file clutter/duplicates? |
Beta Was this translation helpful? Give feedback.




Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
Since January of 2026 I've been working on a separate task for Trilium, called standalone mode.
Standalone mode tries to do something that I haven't seen much in this space: the traditional mechanism of shipping Trilium is either to run the desktop app alone or set up a server whereas standalone ships the server into the client. This means that you can run Trilium in a browser without the need of a server, the database will just live in your browser.
This unlocks the following potential directions:
From a technical point of view, the complexity is quite big with having:
trilium-core).If you'd like to give it a try, see https://app.triliumnotes.org.
The PR is #9189 is quite big (634 commits @ 29k modifications) and it will be merged today. This will cause a significant issue with conflicts on all the branches but solving merge conflicts in all this period has been quite difficult. Since we've just released a major version, it means we have around 2 months to get all the regressions fixed.
While setting up a server for sync makes perfect sense, it also causes a lot of friction since not all users (even power users) are willing to maintain their own server running Trilium. I am aware that Trilium is leaned toward more technical people, but my personal wish is also to get closer to less technical users.
This mode is currently experimental and as such not publicized. For now let's keep the publicity to a minimum, but I would really appreciate some support with testing or feedback.
Let me know your thoughts.
Beta Was this translation helpful? Give feedback.
All reactions