Notes · Wikis · Docs · Tasks
Luzula combines the backlinks of a personal knowledge base, the notebooks and clipping of a classic notes app, and the block editor and databases of a workspace tool — then deploys as 100% serverless infrastructure into an AWS account you control.
Self-hostable · Privacy-first · Apache-2.0 when public · no trackers on this page
Most tools pick one of these lineages and ignore the rest. This one borrows the best ideas from all three, because your notes should not be split across three products with three bills and three data silos.
A networked notebook for thinking.
A filing cabinet for everything else.
A structured workspace for teams.
Ten things it does well. No plugins required, no per-feature upsells, no feature that only exists to keep you subscribed.
Write in a block editor with slash commands, or in Markdown with full fidelity. Both views round-trip cleanly.
Every [[wikilink]] creates a backlink. Follow the graph from any page
to find the notes you forgot you wrote.
Structure anything: tables, boards, calendars and galleries over one set of properties, filters and sorts.
Search every page, title and attachment name with filters for notebook, tag, date and type. Saved searches keep the useful ones around.
Tasks live in your pages and surface in one global task view with due dates, reminders and a daily digest.
Turn any page into a template. One keystroke for today's daily note, wired into your calendar and backlinks.
Owner, editor, commenter and viewer roles per workspace and per page — or publish a page to a public, crawlable URL.
Offline-first: every change is written locally first and synced when the network comes back, with conflict copies when it matters.
Bring in Markdown folders, Obsidian vaults, Evernote ENEX and Notion exports. Leave with Markdown, HTML, JSON or a ZIP of everything.
Clip articles, selections and links from the browser straight into a notebook, through a documented HTTP API you can script yourself.
Not "hosted for you" — deployed into an AWS account that belongs to your organisation. The whole product is serverless: there are no servers to patch, no clusters to babysit, and nothing runs at all until somebody uses it.
Cognito for auth, AppSync for the GraphQL API, DynamoDB for content, Lambda for business logic, S3 for attachments, CloudFront at the edge. Zero servers to manage.
Nobody using it costs (almost) nothing. A quiet workspace at 3 a.m. has no running compute at all — and wakes instantly on the next request.
You pay AWS for requests and storage, not per seat. Small teams typically run for pocket change; you can watch every cent in Cost Explorer.
luzula.config.json at deploy time.
The security story is not a promise about somebody else's data centre. It is your AWS account, your KMS keys, your CloudTrail trail and your auditors' evidence — with a stack that is built to pass the boring questions.
"Ready" means the controls and evidence you need are in place in your account — your auditor certifies your deployment, not ours.
The usual trade: lovely product, somebody else's cloud. Here is what changes when the product runs in your own account.
| Aspect | Luzula | Hosted note apps |
|---|---|---|
| Your data | In your AWS account, under your KMS keys. Export or delete it on your schedule. | In the vendor's cloud, under the vendor's keys and retention rules. |
| Self-hostable | Yes — deploy with CDK into dev, stage and prod. Apache-2.0 when public. | No. Multi-tenant SaaS is the only deployment model. |
| Offline | Offline-first: edits are local before they sync, with conflict copies. | Varies; often read-only caching or none at all. |
| Price model | AWS usage-based — storage and requests, scaling to zero. No per-seat licence. | Per-seat subscription, billed whether or not the workspace is busy. |
| Compliance | SOC 2 and HIPAA ready in your account; sign a BAA with yourself, keep the evidence. | The vendor's attestations, the vendor's subprocessors, the vendor's BAA. |
Placeholder comparison written from common trade-offs — hosted products change quickly, so verify current vendor claims before you rely on them.
Local development needs nothing but Node. Deployment needs one AWS account per environment — and about ten minutes.
The app runs locally against mock data — no AWS account required.
git clone <repo-url> luzula
cd luzula
npm install
npm run devluzula.config.json
One file describes your product name, domains, environments and features. No domain is ever hard-coded in the source.
{
"product": { "name": "Acme KB", "supportEmail": "help@acme.example" },
"environments": {
"dev": { "account": "111111111111", "domain": "kb.dev.acme.example" },
"prod": { "account": "333333333333", "domain": "kb.acme.example" }
}
}Bootstrap each account once, then deploy. With a pipeline account configured, the same command promotes through dev, stage and prod.
npx cdk bootstrap # once per environment account
npm run deploy # synth + deploy through the pipelinePlaceholder These plans are placeholders while the product is pre-launch. Self-hosting your own copy will always be possible, and always free of per-seat licensing.
$0 / forever
Placeholder plan card
$8 / user / month
Placeholder plan card
Let's talk
Placeholder plan card
Spin up a private workspace in minutes — in your cloud, under your keys, on your terms.