Run a real HTML app on a Confluence page
Upload a folder of HTML, CSS and JavaScript. Mini Sites runs it live and interactive on the page — a clickable prototype, a calculator, an explorable diagram. Not a screenshot, not a link. The actual thing.
New Onboarding — Feature Review
Five things people build with it
Run an AI-built clickable prototype inside the PRD it's being reviewed on.
Try the live demo →Turn a formula in a business case into something readers can recompute themselves.
Try the live demo →Click a service or a data flow to see its owner, protocol, dependencies, and risk.
Try the live demo →Replace a static table of region/plan/tier combinations with one that updates live.
Try the live demo →Weight the criteria that matter and watch the ranking recompute, live.
Try the live demo →The problem it solves
A prototype that only runs on your laptop cannot be reviewed by the people who decide on it. The usual workarounds all lose something.
The interaction is gone; reviewers argue about what a click would have done.
One more system to keep alive, one more access list to manage, and it breaks the moment the laptop sleeps.
Fine for a badge or an embed code, not for a multi-file app with its own CSS, JavaScript and assets.
Mini Sites removes the hosting step entirely: the folder you already have goes onto the page where the decision is being made. If what you have is a CI build, a docs export, or an AI-generated bundle rather than a hand-built prototype, see publishing a generated site to a live Confluence page for that specific flow.
How it works
Insert the Mini-Site macro on any Confluence page (type /Mini-Site).
Choose the folder that contains your index.html — nested folders and relative paths resolve exactly as you built them.
The bundle is validated and secret-scanned, then renders inline. Anyone who can view the page can use it.
What you can put on a page
The UI you are asking the team to approve, running, on the page with the PRD.
A chart and a set of filters over a JSON file you ship in the bundle.
A pricing calculator, a checklist generator, a troubleshooting decision tree.
Components rendered from the same CSS the app ships.
Permissions and security
- Confluence permissions are inherited. The app is built on Atlassian Forge; access follows the page. There is no second sharing model to keep in sync.
- The app requests no Confluence API scopes. It does not read your page content.
- Each macro instance runs in its own isolated, non-routable sandbox — there is no public URL to leak.
- Every bundle is validated and secret-scanned before it is served: an index.html at the root, relative paths only, no ../ traversal, and a scan for AWS/GCP keys and tokens.
Limits
| Limit | Value |
|---|---|
| Files per bundle | 2,000 |
| Maximum file size | 25 MiB |
| Maximum bundle size | 50 MiB |
| Required file | index.html at the folder root |
The sandbox is static-only and has no outbound network access — external fonts, CDNs and API calls are not available, so bundle the assets you need. That constraint is deliberate: it is what makes the mini site safe to run inside your wiki.