Neblla has its own backend, and whatever it doesn't use it shares out among its users.DatabaseServerImagesWhen your free space fills up, you can bring your own, and it's still free.
You can go a long way without spending a cent. No paid tools and no card to start. Your app goes live, your friends and first customers try it, and you’re still at zero.
You pay for usage, not for tools or users. Each day’s quota goes to whatever you use, and half of what you don’t spend is saved in a bank: on Saturday you can spend twice as much as on a Tuesday.
We never charge you for anything you didn’t choose. No card, no possible charge. You switch on Pro, packs and auto top-up yourself, and the 1% only exists if you sell with our Stripe integration.
When do we charge? Only in two cases. If you want more limits without bringing your own infrastructure: Pro or a quota pack (see the prices). Or if you sell with Neblla: 1% of what you sell to your users with our Stripe integration; between developers, from 30% down to 2% depending on the price (from €1 to over €50); and 30% if you sell your users items from Neblla, such as assets or 3D game pieces. Stripe's fees are separate. Before that, nothing.
What for
What do you want to build?
Tap an example to see the tools it would use. Whatever you need, Neblla has it.
Yes: it’s designed to get your idea into production without fighting servers. Your AI or the dashboard takes care of the code; Neblla takes care of everything you’d normally need an engineer for: database, sign-in, payments, hosting, backups.
Yes. Four things are yours, and you can take them wherever you like.
⌨️
Your code
With a GitHub repo linked, it already lives in your account. Without one, you download it.
🗄️
Your data
Export your tables and your sales whenever you want. With your own database, they never even leave it.
🖼️
Your images and files
Everything you upload to your app (photos, audio, video, documents), you can download whenever you want.
👥
Your users
You export them with their data and, if they shared it, their email.
What's Neblla's
What happens outside your app: Neblla's community and the reviews and ratings of your app in our gallery.
Ready-made
Do I have to start from scratch?
No. Start from something already made and change it your way.
🎨
Creator: Mundo, Flat and Eco
3D models, 2D drawing and sound, to make your own pieces or use the ones that already exist.
📊
A back office to run your app
It's the panel your users never see and you use every day. There you see who has signed up and answer them, check your sales and refund a payment, open or close spots in a class, moderate what people post, send a notice to everyone or see how many people come in each day. Users, sales, bookings, community, messages, stats, backups and your team with their permissions: they come in the panel from the first minute, with no coding.
🎮
Games
Multiplayer rooms with a shared lobby and matchmaking, scores, counters and card decks kept by Neblla, friends and invitations, a store to sell inside the game, and community. You bring the game.
🧩
Templates
Pick a ready-made style for your web or app and change it with a live preview.
🛍️
Gallery and creators' store
Publish your app on play.neblla.com and buy or sell pieces and templates with other creators.
How Neblla earns
If it's so free, how does Neblla make money?
Straight, so you know before you start.
🏷️
1% of your sales
Only if you charge your users: Neblla keeps 1% of each sale, plus Stripe's fees. If you don't sell, there is nothing to pay for this.
💳
Pro or a quota pack, if you want
Pro is €10 a month per project, and a quota pack is €10 once. You switch them on yourself: without a card, nothing can be charged.
🛍️
The creators' store
Other developers sell what they have made: templates to start your website or app, and assets for Mundo, our 3D game engine, and its community. When a developer buys something from you, the money goes straight to your Stripe account. Neblla keeps a share: 30% on a €1 item, and the percentage goes down as the price goes up, to 2% on anything €50 or more.
☕
If you want to lend a hand
Neblla is a personal project, made with care and at the lowest cost possible. If it works for you and you want to support the project and the person behind it, you can buy us a coffee. It unlocks nothing: it's just a thank you.
Everything included from day one. Pay only for usage.
Accounts, data, rooms, payments and back office come with Free. You only pay if your free quota gets too small and you'd rather not set up your own infrastructure: then we expand it for you.
Recommended
Free
€0
To build your app, test it with friends and publish it. Everything works from the first minute, no card needed. If the quota ever runs out, nothing is lost: running rooms carry on and the quota comes back the next day (00:00 UTC).
For everything
Accounts and login, even without signing up
Data, files and images stored
Hosting with a public URL, or on your site
Back office: users, sales, moderation, stats
Manage it from your AI (MCP) or your GitHub repo
Webs and apps
Bookings with capacity and passes
Store, subscriptions and taxes with Stripe
Inbox with your users, and reminders
Community with moderation and reviews
Games
Real-time rooms and matchmaking
Protected rankings and anti-cheat
Daily challenges, friends and fair draws
Mundo, our 3D engine, with each player's doll
The public gallery and Google Play
Creators
The Creator studios: Mundo, Flat, Eco and Templates
Sell in the creators' store
Limits
1,000 credits a day for the whole account (≈ 36 MB)
300 files and 50 MB of database, shared by your apps
Pro
€10/mo
When an app has people every day and the free quota falls short. Pro is per project: its apps get a quota of their own and your free quota stays whole for the rest. Same features and the same code.
2,000 credits a day for the project, double Free (≈ 72 MB)
600 files and 100 MB of database, also double
2 GB of images and files, twenty times more
The inbox, twenty times more
30-day backups (7 on Free)
Never archived for inactivity
Cancel anytime; it lasts as long as you paid
Quota pack
€10
For a big day: a Saturday tournament, a launch, an event. Pay once, no subscription, and whatever you don't use waits for you for up to 6 months.
14,000 credits, one-time (≈ 500 MB)
Available instantly, with Free or Pro
Used once your daily quota runs out
Auto top-up only if you turn it on, with your cap
Already have something of your own? Use it, on any plan.
Your database, your login, your room server, your CDN or your AI key: plug them in without rewriting your app. Neblla charges nothing for it, and with your own database its storage stops counting.
Pro and packs are per project, taxes included. Outside Europe, the price is $10. The free quota is your account's, shared by the apps of your free projects: creating more apps does not multiply it. If you charge your users with our Stripe integration, Neblla keeps 1% of each sale, plus Stripe's fees. One credit is 35.8 KB of data sent between devices and Neblla; direct P2P messages don't count. A free app nobody opens for 30 days is archived without losing anything and comes back on its own at the next visit.
How you start
How do I start?
Three paths to the same app. Mix them whenever you like.
💬
Ask your AITell your AI what you want and it builds it.
A Neblla app's canonical layout is six files: index.html, main.css, client.js on the front-end, plus three files in a server/ folder split by lifecycle phase — server/lobby.js (matchmaking), server/gathering.js (waiting window before a game starts), and server/room.js (authoritative game logic). Only index.html is strictly required; the rest exist as your app needs them. Client and server communicate through events only — never direct calls (message.send/message.to/state.set + message.on/state.on). In client.js, set window.onNeblla to a callback and it fires once the SDK is ready. The server/ files are loaded by the SDK and run in an isolated scope (no DOM, no neblla.auth) on the room's Fog — three of the users' devices at once, never just the presenter.
Neblla is responsible for your Neblla account. What you give an app belongs to its developer, and Neblla keeps it for them under a data processing agreement. No advertising, no selling your data, no training AI with it.
What needs your attention today and how your app is doing.
Needs your attention
Earlier notices
The last 90 days: what was resolved, seen or ended on its own.
Suggestions
What would make your app better
Settings that cost quota start off. Neblla looks at how your users really use the app over the last 7 days and suggests the ones that would help, with what they cost. Each one is a single change: most land in your draft and reach your users when you publish; the moderation log is the app's own setting and is on at once.
Statistics
How your app grows: how many people come in, where they come from, whether they come back and what they buy.
Keep statistics
at once
Keep my users' statistics
It is your app's own setting, not a version's: it changes the published app and your draft at once, with no need to publish. Turning it off stops the counting; what was counted stays.
Your role in this app's team lets you see the statistics, not turn them on or off.
Neblla keeps them in your app's store: one row per user (first visit, last visit, how many visits and where they came from) and one row of counters per day; with your own database they go there (tables nb_player_stats and nb_stats_days). They are yours: Neblla keeps its own measurement apart and never reads them.
Users
Who uses your app. Each one's card has their data, their suspicion flags and why, their purchases, their credits, and banning or deleting them.
No users.
Select a user to inspect.
Refreshes every 5 seconds
Messages to everyone
Write to all your users
Inbox
What your users write to you (not the chat between them), including requests to erase their data.
Status
From
No messages.
Select a message to read.
Saved replies
Answers you write once and pick when you reply to a user, for example «Class times». Only you and your team see the list; the user gets the text you send.
Inbox settings
Messages between your users and you: they write from your app and you answer here.
Max inbox per user
Leave empty for account default.
Answers by email go to
Someone without an account who writes from your web's contact form gets your reply by email. When they answer it, it goes to this address. Empty: your email.
Welcome message
Every new user finds it in their inbox the first time they sign in, only once. Write {name} where their name goes. Empty: no message.
It was written in several languages through the MCP: this is one of them. Saving here leaves only this text, for everyone.
Requests to erase data
Erasure requests window
Your app can open a Neblla window where the user asks you to erase their data; the request reaches you here, in this Inbox. Turn it off if you handle it your own way.
Moderation
Moderators, cheating, suspicious rooms, legal notices and who banned whom.
Moderators
Users of your app you trust to moderate.More ▸
Moderators are users of your app you trust: they can close any room, make a private room public (when private rooms are on) and moderate the community. They are kept with the data chosen above: a draft with its own data has its own moderators, none at first (add yourself to moderate there).
No moderators yet.
Moderation log
Off by default. Each line costs quota.More ▸
Off by default. On, Neblla writes down who named or removed a moderator, each ban, and every message or community post someone other than its author took down, with who did it and when. Each line costs quota and takes room in your app's storage; with your own database it goes there.
Anticheat
Users' devices check each other's results; here you see what did not agree.More ▸
In some rooms the users' own devices check each other's results. When they do not agree, by default what the one in charge published stands and nobody is marked: the case is kept here as a possible fault in your app. If you turned on «Judge the Fogs by majority», the majority decides and the odd one is marked. If it was a fault in your app and not a cheat, cancel it; if the other two were the ones cheating, move the mark to them.
Without it, cases are deleted 30 days after they open.More ▸
With your own database the cases are kept there and are deleted on their own 30 days after they were opened; on, they stay until you delete them. Without it, Neblla keeps them 30 days. A cancelled case is also copied for Neblla to review, until Neblla closes it.
Purchases claimed without paying
The app on these users' devices claimed more than they bought. Neblla corrected it, and added one flag to the user. It is a notice: nothing else is done to them.
Ban messages
What a user sees when they connect and find themselves banned or terminated. Empty: Neblla's default.More ▸
What a user sees when they connect and find themselves banned or terminated. Plain text. Leave one empty for Neblla's default.
Community
What your users publish and its rules, on one page.
What is happening
No entries.
Select an entry to inspect.
How it works
Community settings
Posts your users publish from your app.More ▸
What your users publish from your app: posts, photos, recipes… Neblla keeps the list and its order; what each post holds is your app's.
Moderation mode
Open: published instantly. Review: pending until you approve. Closed: only moderators publish.
AI pre-screen
An AI reads each entry before it goes live.More ▸
Flag: it is published and shows flagged here, in the list above. Hold: it waits for your approval. Uses your Claude key.
Also look at images
Who can publish
Categories
Comma-separated. Empty = free text.
Content types
Comma-separated labels your app understands (e.g. post, photo). Empty = any.
Community rules
Shown to authors before their first publication.
Limits
Largest size of a post (KB)
What one post can weigh, pictures included. 0 = no limit.
Max entries per user
0 = unlimited.
Votes against
Let users vote entries down too.More ▸
Users always vote entries for. On: they can also vote against, and each entry's score is votes for minus votes against.
Storage used
—
Disputes
Matches whose players said different results: you decide who won, and who cheats.
User groups
Your users' clubs or groups and what each one may do inside (owner, teacher, student).
When users make their groups
Users make their own groups
From your app, a user makes a group and invites others. Whoever makes it gets the role below.
The creator's role
Your app has no roles yet: add them above, in Roles.
Agenda
Your week as a calendar: every class, appointment and match, who is coming, and whether it takes place.
Bookings
Who is coming in the next two weeks, and the credits each client has.
Accounts
What you owe each professional and site, counted from the agenda, and your notes.
Services
What clients book: how long it lasts, how many come, what it needs and how it is paid.
Professionals
Who does the work, with their hours and where they are each day.
Resources
What is booked and how many there are: rooms, tables, baths, courts.
Sites
Where the business is, with the hours of each place.
Ratings
After each session, the clients rate the site and the business rates the clients: see them and hide the ones that should not be there.
Applications
Businesses that ask to be in your app with its form: approve them and each gets its site and its team.
Sellers
Who sells in your app (a club, an artist, an author): each one is paid in their own Stripe account, and you take your commission.
Your team
Who else gets into this panel. What each one can do comes from their groups, and adds up.
Only the app's owner changes the team. You see it read only.
Groups
What each group of your team can do. Someone can be in several groups: their permissions add up.
Only you, the owner, change the team, touch the money (products, plan, taxes) and archive or delete the app: a group can only read those.
+ Add features
Switch on pieces for your app: chat, rankings, shop, bookings, community, AI… The ones that are off do not show in the menu.
Modules
arrives when you publish
Your app is made of modules. A module that is off is not in your app, Neblla refuses its calls, its pages leave this dashboard and the docs for your agent leave it out.
Rooms
The open rooms and who is in each one right now, their chat and how they are formed.
What is happening
No rooms.
Select a room to inspect.
How it works
Room settings
Places where several users are at the same time.More ▸
Places where several users are at the same time: they see each other, talk and share data. Your app opens them; here you choose which kinds there are and their limits.
Room types
Ephemeral: it lasts while someone is in it; then the room and its chat are gone. The default.
Public: it stays and keeps its chat. Anyone in your app can come in.
Private: it stays, with an allowed list its owners manage.
Default type
The kind a room gets when your app does not say which.
Rooms only with a login
Whoever has not signed in stays at the entrance.More ▸
Whoever has not signed in stays at the entrance (the lobby), and your app asks them to sign in to go into a room. Private rooms always ask for it.
If your server goes down, Fog takes over
The room moves to a user's device and back. On by default.More ▸
The room moves to a user's device with the same room.js, and back to your server when it returns. It costs nothing. On by default.
Limits
The most a room keeps (KB)
What a room keeps. 64 KB is a few pages of text. 0 = no limit.More ▸
How much what a room keeps may take up, in KB (64 KB is a few pages of text). 0 = no limit. Empty: about 10 KB. The entrance (the lobby) takes 10 times this.
KB
Limits of the
Users can create
Off: only you make public rooms, from this panel.
Per-user limit
How many public rooms a single user can create. 0 = unlimited.
Delete it after this many days unused
Rooms nobody uses for this many days are deleted. 0 = never.
Per-user create limit
How many private rooms a single user can create. 0 = unlimited.
Per-user participation limit
How many private rooms a single user can be a member of at once. 0 = unlimited.
Delete it after this many days unused
Rooms nobody uses for this many days are deleted. 0 = never.
When a room starts
When a room that waits for people starts.More ▸
Decides when a room that waits for people starts. Custom: your app's code decides it. No-code: pick a rule below and Neblla writes that code for you when you save (changes made to it by hand are overwritten while no-code is on).
Mode
Start rule
When does the room start?
Fewest users
Most users
0 = unlimited. When reached, the room starts immediately.
Wait (seconds)
Presenter can start early
Whoever leads the room can start it before the rule is met.
When you save, Neblla writes again the code that decides when the room starts.
Games with a winner
Data and your database
Your app's tables and their rows, what each user saves, the backups and your own database.
Backups
Every day Neblla keeps an encrypted copy of your app's data: the users, what they save, your tables, the inbox, the community, the chat, the rooms and the purchases. Here are the last 7 days, or 30 with Pro. You can put one back whole, for the published one or for the draft.
Loading the backups…
Tables
The tables your app keeps. Each user reads and writes their own rows.
What other users see
What of each user's saves other users may read in your app (neblla.db.dataOf(user), neblla.db.loadOf(user, { table })): everyone, or only their friends.
Trades between users
What one user may give another in exchange for something of theirs (neblla.db.offer({ to, give, get })): it happens only when the other accepts, all at once.
Packs and draws
Packs of cards, a surprise box, a daily prize: what each opening deals, decided by Neblla and never by the app (neblla.db.draw(name)).
Rows of the tables
Every user's rows, to look something up or fix it by hand. Filter by user or by a field.
Database — bring your own
By default Neblla keeps your app's data (what each user saves, the rooms and their chat, the messages, the community and your tables) in its own store, which counts toward your quota. You can take it to your own database: everything of your app goes there, at no storage cost and under your control, your users, their purchases and their bans, the anti-cheat cases and the legal notices too: the originals are there. Neblla keeps only what is its own: a pointer to each player, its own count of visits, the cases it reviews and a minimal copy of the legal notices. Connection strings and tokens are encrypted at rest; the browser never sees them again after submit.
Database of the environment you chose at the top
Loading current backend…
Migration in progress
Your app's data is in your own database. Going back copies all of it to Neblla's, like any migration, and is paid from your app's quota.
Engine
What "Start migration" does: the migration runs in three phases. (1) Live bulk copy of all user data to your database. (2) Live delta copy of anything that changed during phase 1. (3) A brief lock (seconds) to copy the final delta and switch the pointer. Your app emits an 'app_maintenance' event during phase 3 so you can show your users a "we'll be right back" message. Total time depends on data volume; typical is minutes for an indie app. Going back to Neblla's database is the same migration the other way. Every migration is paid from your app's quota (the reads, writes and bytes it moves): if the quota runs out, the copy pauses and goes on by itself after the daily reset or when you add credits; the brief lock always ends, and what it moves is charged too.
Scores and rankings
The rankings of your game: which score wins in each one and the limits a real game cannot pass. Neblla checks every score before it enters.
Rankings
arrives when you publish
Each ranking keeps the best score of each user and of each day. A score that breaks its limits does not enter.
AI
Your app's AI: model, limits per user and what it spends.
AI
arrives when you publish
Your app's AI is on
Your app can ask the AI for answers. It is switched on and off in Functions › + Add functions.
It has no settings yet: until you set it up, your app's calls to the AI are refused.
Who pays the AI
Whose key
Yours: the calls use your key with the provider; your limit per user applies. The user's, from their browser: each user puts their own key and the call leaves from their browser. The instructions you give the AI can be read in the page. The user's, through Neblla: each user puts their own key and the call goes through Neblla, which adds your instructions. They stay private.
Ready-made instructions
Instructions with a name that go in front of what the user asks, for example «short»: «Answer kindly, in two sentences at most». Your app chooses which one each question uses.
Limits
A daily limit for each user
How much each user can use the AI per day, so that nobody empties your key. Only when the key is yours.
Tokens per user, per day
A token is a piece of a word: 10,000 is about 7,500 words, questions and answers together. Counted over the last 24 hours; past it, that user's calls are refused until the count goes down.
Provider keys
arrives when you publish
Pick the provider your app uses: only one at a time. Its key is used when the key is yours.
ClaudeNot connected
API key
Anthropic key. Managed in your account.
Model
The most expensive model users can use with your key. They can ask for a cheaper one.
Max output tokens
Per response. Default 1024.
OpenAINot connected
API key
OpenAI key, saved encrypted in your account.
Model
The most expensive model users can use with your key. They can ask for a cheaper one.
Max output tokens
Per response. Default 1024.
DeepSeekNot connected
API key
DeepSeek key, saved encrypted in your account.
DeepSeek is not called from the browser: with your users' own keys, use the Server mode.
Model
The most expensive model users can use with your key. They can ask for a cheaper one.
Max output tokens
Per response. Default 1024.
Custom screens
Screens you make to see and touch your data, for you or for someone on your team.
Make one here, or your AI makes it for you: ask it «make me a screen with today's bookings».
Where the games run
On your users' devices, on your own server, on your Cloudflare or in Neblla's cloud.
Server mode
arrives when you publish
Where the server/ files (server/lobby.js, server/gathering.js, server/room.js) run, and how exposed they are to inspection. Whatever you pick, the same code keeps working — that's the point of the events-only contract.
Connection between devices
How devices connect to each other and what to do with whoever cannot.
How they connectarrives when you publish
Por defecto los dispositivos se conectan directamente entre sí (P2P), sin pasar por Neblla: es gratis y no consume cuota. Si en una red no es posible la conexión directa, Neblla puede mediar el tráfico — eso sí consume cuota (no pasa por la RAM de tu app, es solo reenvío de red).
P2P directo entre dispositivos
Conexión directa (WebRTC). Gratis. Necesaria para la transferencia de ficheros P2P. Por defecto activado.
Si no hay P2P, que Neblla medieconsume cuota
Mantiene la conexión en redes restrictivas (NAT simétrico, firewall) reenviando el tráfico por un relay de Neblla. Asumible para datos pequeños (p. ej. ajedrez); para file-transfer o drawing board puede ser caro — tú decides por app.
🔒 La mediación consume cuota y se activa cuando el relay TURN está desplegado en el servidor de Neblla.
Backup through Neblla's serverconsume cuota
The last resort, after direct P2P and the TURN relay: what cannot travel that way goes through Neblla's server (it counts against the quota). Off by default.
Watch impossible send timesconsume cuota
Marks a user whose messages claim a send time that cannot be, a sign of a tampered client. Each check costs quota. Off by default.
Keep the screen on in rooms
While a room's server code runs, the player's screen does not lock. A phone that locks drops out of the game; this costs a little battery only while playing. On by default.
Judge the Fogs by majority
When the Fogs of a room disagree, the state the one in charge published stands and nobody is flagged. Turn it on to let the majority of stable replicas decide and flag the odd one. Off by default.
Direct clicks between devices
A player's message to the room's server code goes straight to the devices that run it, not through Neblla: faster, and it costs no quota. Neblla keeps a copy only for a device with no direct link. Test it in your app before turning it on for everyone. Off by default.
Products
What you sell and its prices: one-off purchases, bundles and subscriptions.
🛍
Select a product on the left or create a new one.
How it works
Shop
Buy without signing up
A user buys leaving only their email at the payment, and the purchase works at once; on another device they get it back with that email. Off: buying asks them to sign in first, and the purchase goes on once they are in. On by default.
Signature and coffee
Shows Neblla's logo and a coffee cup on the top bar.
Passes for bookingsFixed places
Sales
The purchases made, with the test ones marked, the refunds and the invoices.
Orders
Each payment of a physical product, with the address to send it to. Mark it shipped with its tracking number, and delivered when it arrives: the buyer hears each step in their inbox. From the delivery, the buyer has 14 days to withdraw (EU).
«Refund» gives the whole payment back from your Stripe account, at once, and the user loses what they bought. «Receipt» and «Invoices» open what Stripe gave the buyer. The CSV takes every sale that matches the filters, for a spreadsheet.
Payouts (Stripe and taxes)
Your account to get paid and how taxes are worked out.
Your Stripe account
Taxes on this app's sales
at once
Work out the tax automatically (Stripe Tax)
Stripe adds the right tax for each buyer's country to this app's checkouts. It needs your tax settings in Stripe to be active (head office and where you are registered); until they are, it is not applied.
Prices already include the tax
On: the buyer pays the price you set and the tax comes out of it (usual when you sell to people in Europe). Off: the tax is added on top (usual for businesses or the US). Neblla's 1 % is always on the amount before tax.
Tokens
The app's own balance: bought in packs and spent inside. Settings and notices.
Loading…
Tokens report
How much was sold, spent and what is still alive, with the surplus and disputes.
Loading…
Vendors and their products
Who sells in your app (stalls, shops), their catalogue, what you owe them and what you paid.
Loading…
Plan and usage
What Neblla costs you: how much you have used, packs, the paid plan and automatic top-up.
Capacity
Most per userat once
The most one user may spend of the app's daily quota, in % (20 by default; 0 = no cap). Past it, Neblla refuses what that user's app asks for until 00:00 UTC; everyone else carries on.
%
Most saved per userarrives when you publish
The most what one user saves may weigh, in KB (0 = no limit). Past it, that save is not made and your app is told why. Empty: the default.
KB
Breakdown will appear here once your app has traffic.
Code
Your app's files, the preview, the version history and GitHub.
Live preview · draft
Edit with AI
Ask the AI for changes and you will see them in your draft.
✨
Describe changes, ask questions, or paste errors. Selected files on the left are the context.
🤖
Claude not connected
Connect your Anthropic API key to edit files with AI. Usage is billed directly to your Anthropic
account.
Media
Photos, textures and sounds of your app, apart from its files. What you change here is live at once, with nothing to publish.
Drag the pictures to put them in order. Click one to edit its card.
Look
Colours and fonts.
Theme
arrives when you publish
Opens Templates with this app already chosen: three questions and done.
Errors and refusals
What failed in your app's code, what Neblla refused it and the webhooks that did not arrive: the first place to look when something fails.
● Live
Webhooks
Tell other programs: each purchase, booking or sign-up notifies your CRM, Slack or whatever you like. Also what comes in from outside.
Scheduled tasks
Things that happen on their own at a time: «every Monday at 9:00, send a reminder».
Automations
at once
Scheduled actions, without a server of yours: open a room with its starting data (config), hand a message to a room's room.js (the file of your app that acts as that room's server), or call another service with one of your secrets (Build › Keys and secrets) — once, every N minutes, or daily at a time in your time zone.
Keys and secrets
Values your app needs: the public ones, the secret ones and your server's key.
Keysarrives when you publish
Values your app reads with neblla.api.key(name), to change something without touching code: an event, a multiplier, today's challenge. Text, number, yes/no or JSON. They are public: never put a secret in a key.
Code for your external website
The snippet to use Neblla from a website that is not hosted here.
Draft and published
The draft holds the changes nobody sees yet. Publishing sends them to your users, all at once.
Your app is online
It has been online since you created it. Anyone with this link can open it:
Real is what your users use. Prueba is a private copy to try changes. Choose one at the top; «Guardar» saves in the one you chose and «Publicar» sends what you saved in Prueba to Real.
Go back
The last versions your users had. «Go back to this one» publishes that version again, whole, at once. Your draft does not change.
Who sees the draft
Neblla accounts
Links with a password
Data and purchases of the draft
From your computer (localhost)
A page on localhost opens only the draft, and only with this tag, which carries your app's local key. Put it in your local index.html instead of the usual one. Never publish it: if it leaks, renew it and the old one stops working. Test here, not on the published web: your files here cost no quota, while every file a published page serves costs about 1 credit (charged the next day), and the quota belongs to the whole account.
Gallery and reviews
Your listing in Neblla's public gallery, its translations and what people think of your app.
Not in the gallery
This app isn't listed in the public gallery. Toggle on and save to list it.
Image and kind
No image
Title and description
It is listed in the gallery in the languages you write it in.
EN
ES
FR
DE
IT
PT
JA
KO
ZH
AR
Reviews
⏳
Loading reviews…
Link and allowed websites
Your app's link on Neblla, and which of your websites may use it.
play.neblla.com/
5–50 characters. Lowercase letters, digits and hyphens. Optional but unique.
Websites that may use your app
Restringe/añade dónde puede usarse el SDK. Un dominio por línea.
This list only lets your websites use your app; it does not open your app there. To open your app at a domain of yours, use Publish › Your own domain.Go to Your own domain
Compiled app and new guests
Compiled app
For Capacitor, Ionic or Tauri, which arrive without a domain. New guests from one address are limited. To try your app from localhost, use the tag in Publish › Draft and published: it opens your draft.
Platforms it is compiled for
Anyone’s website can embed your app in a sandboxed iframe, so Electron opens the door wider. New guests from one address are still limited.
Turnstile for new guests
Before a new guest is made, Cloudflare checks it is a person, almost always without asking anything. It stops scripts creating guests by the thousand. Users who come back are not asked.
On a domain of your own, Neblla's widget does not work: create one in Cloudflare (Turnstile, free) and paste its keys.
Dominios automáticos
Tu app responde en todas estas URLs sin que configures nada (por id y por slug, en los dominios de Neblla + Cloudflare).
Your own domain
Your app at a domain of yours, like mygame.com, instead of its link on Neblla.
Loading…
Google Play and other stores
Publish your app as a mobile app.
General
Name, identifier, state and copying settings from another app.
Name
at once
Identifier
Your AI and the SDK know your app by it.
—⧉
Project
The project this app belongs to.
State
Example app
at once
Show it as an example
For others to see how it is done. It always charges in Stripe's test mode: anyone buys with the card 4242 4242 4242 4242 and nothing is charged. Its address ends in -example, the gallery does not list it, and each time you publish its code goes to your public GitHub repo of examples.
Copiar configuración de otra app
arrives when you publish
Clona ajustes de comportamiento (funciones, salas, emparejamiento, IA, P2P, permisos, tema) de otra de tus apps. No copia identidad, dominios ni hosting.
Notices
What Neblla tells you about, to whom and how. Everything also stays in Home, with its history.
Activity log
Who changed what and when: your team, your moderators and what your AI did.
Data you ask your users for
Which data you ask for (email, friends…) and the sentence that explains why.
Permissions
arrives when you publish
When users open your app, Neblla shows a consent screen for the data your app wants to read about them. Each scope below has a justification you write — it appears verbatim, in quotes, with your app's name, in the user's gallery permissions screen and in the consent popup. A clear, honest reason gets more yes's; vague or absent text makes users default to no. Max 200 characters per scope.
📧 See user email
Optional. Email is not required for any app to function — Neblla identifies users internally. Only ask for it if your use case truly needs it: cross-referencing accounts between your apps, importing data from systems outside Neblla, or sending email outside the platform. Users see this as a serious request and many will refuse without a strong reason.
👥 See user's friends list
Useful for social features: invite friends to a room, show who's online in your app, share a list or a plan with them. Users grant this more readily than email — but the explanation still helps.
📡 Be visible to friends inside this app
When granted, this user appears as online inside your app to their friends — enabling room invites, joining a friend's room, and presence indicators. Without this, friends can read each other's friend list but can't tell who's currently in your app.
🪪 See the user's Neblla name and photo
Optional. Only ask for it if your app shows who is signed in with their Neblla name and profile picture, for example in a header. Without it the app only gets an anonymous identity.
Your own login
Let your users sign in with your own login system.
Your own login
at once
If your app already has its own users, your server uses this secret key to get a one-use login token for each of them. It is shown only once: keep it on your server, never in the app. Whoever has it can sign in as any user.
Archive or delete
Archiving can be undone; deleting cannot.
Archive the app
Its users, rooms, messages, products and files are packed into one sealed file in Neblla's private store and leave Neblla's database. The next visit brings it back on its own; that first visit takes 1–3 s.
Danger zone
at once
Delete this app
Permanently remove the app, all its files and its gallery listing. This
cannot be undone.
To sell it you need a Stripe account; Stripe sets it up with you in a few minutes, and if you already use Stripe you sign in with it. The product is saved now and publishes by itself as soon as the account is active.
Ask about your app
An AI that has read this app's settings and Neblla's documentation answers you. It changes nothing: it tells you where to do it. It runs on your Claude key, so each question costs you a few cents with Anthropic; Neblla charges nothing for it.
You have no Claude key savedThe AI answers with your own Claude key, as Edit with AI does. Save it once in your account (Account › Claude). Until then, you can write to a person at Neblla.
Public Info
Your public name and picture. The name will appear as the owner of all your apps.
✎
Messages from other users will be automatically translated into this language.
Saved!
Your studio
The public page of all your published apps, with their ratings, reviews and subscriptions. Its name is your public name. It is also the web of your business on Stripe.
Your page:
Saved!
Email Addresses
Manage email addresses linked to your account. The primary email is used for notifications.
Loading…
Password
Choose a strong password — at least 8 characters.
My notices
Of what reaches you from the apps you are on, take away what you do not want: a type, a channel, or the small ones.
Notifications on this phone
Neblla tells this phone about the urgent alerts of your apps and new messages in the Inbox.
My role
The apps you work on and what your role lets you do in each one.
💳
Stripe Connect
Accept payments directly in your apps. You keep the money — Neblla takes a small platform fee.
Loading…
Loading…
🐙
GitHub
Sign in with it, link an app to one of your repos and publish your example apps.
Loading…
Loading…
🤖
Anthropic Claude
Add your API key for unlimited AI-powered file edits using your own account.
Not connected
Your key is stored encrypted and only used for AI edits you request. It never leaves Neblla's backend and is not shared with the client.
The AIs (Claude, ChatGPT…) you have allowed to work on your account through Neblla's MCP. Removing the access stops it at once; the AI has to ask you again, and you will see the authorization screen.
Loading…
Notices
What Neblla tells you about, where it goes (email, Telegram, your phone) and with which filters. Your projects and apps inherit this and can change it.
API Token
Your session lasts 30 days after your last visit. Rotating the token invalidates the current one immediately.
Projects
A project is the pocket that pays: its apps share the quota, Pro and the connections (Stripe, Cloudflare, database). A folder is only how you sort your list.
Delete Account
This will permanently delete your account, all your apps, and all associated data. This cannot be undone.
Attention
Notices from Neblla
Changes Neblla announces to every developer.
Projects
Each project has its apps, its team and its notices.