No-code apps and databases decision
widgetly
A technical user can build a useful subset (create/embed widgets and handle billing) but reproducing the full polished product and multi-widget catalogue with high-volume hosting is a multi-week effort; existing open-source widget projects reduce work but don't fully replace the paid product.
Visit website↗$3/mo
$36/yr
Read off the official pricing page.
$100one-off76 h to build
$25/mo6 h/mo upkeep
On cash alone, building overtakes the subscription at 12 seats.
Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All widgetly alternatives, with the arithmetic →
What a replacement has to do
- Create a widget definition in a web UI, store the widget configuration, render an embeddable widget script that fetches configuration and displays the widget in Notion or a website, and optionally gate access/payment.
What it still won’t have
- Polished UI/UX and variety of prebuilt widget templates
- Built-in analytics and high-volume view handling shown on pricing page
- Integrated billing dashboard and hosted payment gates
- Ongoing product support, marketing, and reliability guarantees
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 12 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal self-hosted Notion widget service using React for the dashboard, Node.js + Express for the API, and Postgres for persistence. Core features: (1) user sign-up and simple account record, (2) dashboard UI to create/edit widget configs with preview (button, counter, simple progress bar), (3) REST API to store/retrieve widget configs, (4) embeddable renderer script (single JS file served via CDN) that fetches widget config by ID and renders into a host page, (5) Stripe integration for a single paid tier that unlocks higher view limits, (6) basic access gating via token query param, (7) deploy instructions for a VPS or cloud provider and serving the renderer via a CDN. Out of scope: advanced widget catalogue, analytics dashboard, complex widgets (weather, calendar), and marketplace features. Include error handling, input validation, and unit tests for API endpoints.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 5 cited sources+3
- Price verified on pricing page+3
- Evidence score63
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 5
Every page the run actually retrieved.
- official productwidgetly - Widgets Made for Notion
- official pricingwidgetly pricing
- official docsButton Widget
- open sourcenocodb/nocodb
- open sourcedirectus/directus
Integrity checks
What held up, and what did not.
