White-label embed
A notebook inside your app
Allied Note is designed so another product can embed it instead of building notes again. This is the design. The embed is not built, and there is nothing to install yet.
-
No second login Planned
Your server signs a short-lived token for your user, naming the user, their workspace and their role. The embed trusts that token. Your users never see an Allied Note sign-in screen.
-
Styled as yours Planned
Theming by tokens for color, corner radius and type. An optional custom domain. The “Powered by Nabu” badge is planned to be removable on paid white-label plans.
-
Embed only what you need Planned
The full notebook, a single page, the today view, a task list or a capture box, each embeddable on its own.
-
Two-way events Planned
Your app will be able to open a page or react to a change, through browser messages between your page and the embed.
Why it should hold up
- Host apps are part of the data model from the start. An app that embeds Allied Note is a first-class record with its own keys, theme and allowed origins. Tenancy is in the first database migration, not added later.
- The embed uses the public API. So does our own web app. There is no private path that the embed lacks.
- We are the first customer. The first host app will be one of our own products, replacing the notes feature it has today. The embed is being designed against that real need.
- Your users can stay yours. A user of your app will be able to link a network account later and see the same notes at alliednote.com, but only if you, the host, allow it.
What is not decided
- White-label pricing. No price is set.
- The license for the embed package. It will be open source, with the license to be announced.
- Timing. The embed is phase 8 of 9 on the roadmap, and may move earlier.