01 / 03
Super App
One seamless shell, endless modular apps. Ship independently while sharing identity, payments, and native device capabilities.
1NebulaAPI.openApp('ride-hailing')PaymentsRide hailingFood deliveryShopping
Examples
One runtime, three ways to ship
A super app, an AI coding agent, or a fully native shell — every miniapp is still independently built, distributed, and updated.
02 / 03
Coding Agent
Integrate an LLM with an MCP server to create, build, and publish miniapps through governed tools.
$ agent "Build a travel planner"
|
v
[LLM] plans the miniapp and selects MCP tools
|
v
[MCP] create_project
|
+--> build_project
|
+--> deploy_project
|
v
[Cloud] release published
|
v
[User] Open MiniApp -> install and run in hostLLM tool callsMCP integrationCloud building
03 / 03
Embed in native apps
Keep your native app shell, navigation, and product identity while opening independently shipped miniapps from Nebula Cloud.
1NebulaHost.shared.setServerBaseURL(
2 "https://cloud.example.com/api"
3)
4
5NebulaHost.shared.openApp(
6 "superapp-travel",
7 from: navigationController,
8 initialProps: ["entry": "home"]
9) { error in
10 if let error { present(error) }
11}Keep your app UINebula SDK
Capabilities
Everything you need to run, update, and manage Miniapps in a React Native application.
Runtime boundary
Sandbox isolation
Each miniapp gets its own storage namespace, file root, and runtime state, and can only call capabilities the host has explicitly registered.
Capability APIs
Base library
Device, network, media, and storage capabilities ship as standard async APIs, implemented once by the host and shared across miniapps.
@nebula-rn/components
Cross-platform components
Swiper, Video, Map, Camera, WebView and more ship as a separate package, installed on demand instead of bundled into the base library.
Lifecycle hooks
Page lifecycle
onLoad, onShow, onReady, onHide and onUnload map native page callbacks to hooks, from cold start to cached revisit.
Capability model
Extensible Host APIs
Hosts register business capabilities such as payments or membership through versioned contracts; miniapps detect support and degrade gracefully.
Distribution
OTA delivery
Complete bundles are downloaded, cached, and opened offline. Updates land without an app-store release, on automatic or manual strategies.
Developer experience
Dev Runner
A universal debug host in the spirit of Expo Go: develop and hot-reload miniapps without the full host app, with simulated capabilities.
Toolchain
CLI & templates
Scaffold hosts and miniapps from built-in templates, then run dev, build, and upload from one command line — @nebula-rn/cli.
Control plane
Nebula Cloud
Self-hostable backend for uploads, experience and production channels, and one-click rollback to any published version — Docker included.
Roadmap
What's next
Capabilities we are designing toward. They reflect current plans, not committed timelines.
Web support
Run both the Nebula host and miniapps on the web.
Planned
JavaScript sandbox
Restrict direct access to arbitrary native modules and make the host boundary more auditable.
Planned
MCP server
Expose host, miniapp, API, and capability context to AI tooling and automation workflows.
Planned
Documentation automation
Generate and validate reference docs from structured API metadata so docs and code drift less often.
Planned
Host API guard
Add fine-grained policy controls for API exposure, runtime validation, and access restrictions.
Planned
NEBULA
A React Native-powered solution for running mini-apps, with host runtime, isolated containers, preloading, and extensible base-library APIs.
View docs