What Cloud adds
BlockNext Cloud is the same platform, hosted for you at platform.blocknext.ai. Every node, credential type, trigger and MCP server in this documentation exists in both editions — the canvas, the $reference model and the credential security model are identical. What follows is the complete list of differences.
You skip the infrastructure
Section titled “You skip the infrastructure”There is no .env, no Docker, no database to back up and no version to upgrade. The Self-hosting and Configuration sections do not apply to you; everything else does.
OAuth apps are already registered
Section titled “OAuth apps are already registered”Self-hosting, a node that authenticates via OAuth needs you to register an app with the provider first. On Cloud, the common providers are already registered, so connecting Google, Slack or Discord is a consent screen and nothing else. This is the platform credential source described in the credentials reference — the token stored on your credential is still yours, and still encrypted at rest.
You can always supply your own client instead; owner-source credentials work exactly as they do self-hosted.
AI features are on
Section titled “AI features are on”“Describe it, don’t configure it” and AI flow generation both need an LLM behind them. Self-hosting, they are off until you provide a key of your own. On Cloud they are available on every account and are paid for with credits.
Runs cost credits
Section titled “Runs cost credits”Self-hosting, the only ceiling is your server. On Cloud each run debits credits from your organization, and your plan sets the limits that apply to it — how many workflows you can keep, how many members can join, how many runs go at once. See Plans & credits.
There is a marketplace
Section titled “There is a marketplace”Cloud accounts can publish workflows for others to buy and add purchased ones to their own library. Nothing equivalent ships in the self-hosted edition. See Marketplace & library.
Getting help
Section titled “Getting help”Cloud accounts open support tickets from inside the app — a ticket carries a type (bug, feature request, question, other), a description and file attachments, and the reply thread stays on the ticket.
Self-hosting, support is the issue tracker and the security policy for anything sensitive.