SilverBullet Hosting

How SilverBullet works

SilverBullet stores a knowledge space as Markdown-oriented pages and builds indexes that understand links, tags, tasks, objects, and other page metadata. Wiki links and backlinks connect related ideas without forcing every page into one fixed folder. Queries can surface matching objects or tasks, while templates and commands reduce repetition in recurring notes and personal workflows.

Space Lua makes the knowledge base programmable. Scripts can calculate values, transform pages, create commands, render widgets, query indexed data, and automate actions inside the space. That flexibility also creates a trust boundary: imported scripts, plugs, templates, and code notes should be reviewed before activation because they can affect data and behaviour beyond ordinary text editing.

Key SilverBullet features

The catalogue sets SB_USER with an admin username and a generated password, which forces SilverBullet into authenticated single-space mode. One persistent /space volume holds the knowledge files and related runtime data. This is a focused personal or trusted-group deployment, not the broader multi-space account manager described by newer upstream documentation.

The web client can synchronise a copy of the space for responsive and offline-oriented work, while the server remains the shared source for updates. External command clients and third-party plugs are not included. Large attachments, complex indexes, frequent script execution, or many connected browsers can move demand beyond the light footprint of plain Markdown pages.

SilverBullet vs Notion

SilverBullet centres on Markdown pages, wiki links, queryable objects, scripts, and a programmable personal space. Notion provides a hosted workspace for documents, databases, projects, collaboration, permissions, integrations, and provider-managed clients. Both can organise knowledge, but their storage, extensibility, and administration models are substantially different.

Notion may suit teams that want polished managed collaboration and a broad vendor ecosystem without running infrastructure. SilverBullet is a better fit for technically confident users who value text-oriented data and programmable behaviour. Its scripting model demands more care, and the catalogue’s single-space credentials do not reproduce Notion-style organisation administration.

Who uses SilverBullet

Developers maintain design notes and snippets, researchers connect concepts through links and objects, and individuals build task or journaling systems around their own conventions. SilverBullet is particularly useful when a fixed note-taking interface feels restrictive and the user is comfortable treating parts of the knowledge base as code.

It is less suitable for organisations expecting turnkey document governance, formal records retention, non-technical workspace administration, or provider-supported integrations. Sensitive material should be protected with strong credentials, and any code imported from another person should be evaluated like an application extension rather than ordinary prose.

Self-hosting SilverBullet: requirements and cost

SilverBullet resource use grows with page count, attachment size, index complexity, active browser clients, query frequency, script execution, templates, and plug activity. PostgreSQL and MariaDB are Not required in the catalogue template; the /space volume holds the Markdown-oriented knowledge data. Plain notes are light, while large attachments and automation-heavy spaces need closer observation.

On AvaHost, SilverBullet uses Plan 1 at €2. The hosted SilverBullet package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. The catalogue provides one generated single-space login. Multi-space administration, external command clients, third-party plugs, code review, and consulting for custom Space Lua are not included. Install only trusted scripts and retain independent copies of important Markdown content.