VS
Vendor bid scorecardvendor-scorecard.html
- Built with
- Claude
- Uses
- Local CSV
For self-contained browser apps
Your app is built.
Now send it.
DotSmall turns a finished browser app into one stable link. Your recipient opens it without an account, uses their own files and local data, and gets the result without sending that working data back to you.
- No recipient sign-up
- Local files stay local
- Version or revoke anytime
dotsmall/s/vendor-review↗
Vendor bid scorecardShared by Northline Procurement
Local fileNo accountNetwork blocked
Package self-contained exports from
ChatGPTClaudeReplitLovablev0BoltGeminiHTML
From finished app to usable handoff
Built anywhere.
Delivered through DotSmall.
AI builders help you make the app. DotSmall handles what happens after: packaging, publishing, opening, updating and revoking it.
A
your-app.htmlself-contained browser app
Bring the finished app
Choose one HTML file or an existing .small package. Packaging reads the app as data and does not execute it.
Files complete✓Network free✓No secrets found✓
Check and publish
DotSmall records the files, capabilities, known limits and exact content fingerprint, then creates one stable link.
Recipient
No account requiredYour recipient uses it
They open the link, choose their own local files or enter their own data, finish the task and export the result.
Four practical starting points
Apps people
actually send.
Not another calculator. Each example gives another person a reusable workflow for a complete job while keeping their working data on their device.
Northstarranks first on delivery confidence
Delivery confidence92%
Price position2 of 3
Open risks1
Northstar takes the lead when implementation timing and reference quality matter more than the lowest price.
A handoff, not another platform to learn
Simple for the recipient.
Controlled by the creator.
Open the link. Use the app.
The recipient does not need DotSmall, the original AI builder, a setup guide or an account.
Shared link→Useful appNo sign-up
Their data stays theirs.
Selected files, answers, local state and generated results stay in the recipient’s browser session.
Recipient device
CSVNotesResult
Not sent to the creatorUpdate without changing the link.
Publish a new version, roll back to an earlier one or revoke the app completely.
v3 Livev2 v1 Original
Fork the workflow. Never the recipient data.
When the creator allows it, an invited creator can copy the app into their own workspace. The original recipient’s files, answers and saved state do not travel with the fork.
Original app→New creator copy0 recipient records copied
The data boundary
The app travels.
The work stays local.
DotSmall stores what is required to deliver and manage the app. It does not need the private material a recipient uses inside it.
The software handoff
- Published app package
- Version history and publication status
- Aggregate open, start, complete and export events
- Feedback the recipient chooses to send
The recipient’s work
- Files they choose inside the app
- Answers, notes and working state
- Locally generated results
- Private data carried into an official fork
Current compatibility
Will your app
work in DotSmall?
The builder name does not decide compatibility. The exported app does. The first release is deliberately narrow so every recipient gets a predictable experience.
Self-contained local browser apps
- One finished HTML file
- User-selected local files
- Forms, visual controls and deterministic logic
- Local state and generated downloads
Packages that need more runtime support
- Multi-file static packages
- Existing .small packages
- Apps requiring a build step
- Features not supported by the local runtime
Apps that depend on remote systems
- Backends, databases or private APIs
- Remote assets, AI calls or external accounts
- Payments, secrets or credentials
- Service workers, frames or navigation
Straight answers
What DotSmall is.
What it is not.
What is DotSmall in plain English?
It is a delivery layer for small, self-contained browser apps. A creator publishes the finished app to one stable link. A recipient opens the link, uses the app with their own local input and does not need an account.
Why not just email a ZIP?
A ZIP can be enough for a technical recipient who trusts and understands the files. DotSmall adds a stable link, repeatable package checks, an exact content fingerprint, version history, rollback, revocation and a clear recipient page.
How is this different from Vercel or Netlify?
Those services host conventional web applications. DotSmall is for portable local tools where the recipient supplies the working data. It is not a replacement for normal hosting when an app needs a backend, live API or shared database.
Can I use an app from Lovable, Replit, ChatGPT or Claude?
Yes, if the exported result is a self-contained browser app. If it still depends on the builder, remote assets, a backend or private credentials, it does not fit the current local runtime.
Does the recipient need a DotSmall account?
No. Creator tools require an invited account. A recipient can open a published app link, use the app and export the result without signing up.
Does local mean completely safe?
No. DotSmall checks common source patterns, verifies the package and opens accepted apps with restricted browser privileges. Those controls reduce risk but do not prove arbitrary code is harmless. Recipients should still trust the person who sent the app.
Can the app call an AI model?
Not in the first release. The current runtime blocks network-dependent apps. Managed AI, paid recipient sessions and bring-your-own-provider options belong to later releases and are not presented as current features.
What can the creator control?
An invited creator can publish a stable link, release new immutable versions, roll back, revoke or restore the app, choose whether official forks are allowed and see bounded aggregate usage.
Early creator access
Built something
worth sending?
Tell me what the app helps someone do and who needs to receive it. If it fits the current local format, I will invite you to package and publish it.