Base44 vs Blink (2026)

Prebuilt integrations cover AI, email, file storage, payments and messaging, with Airtable, Slack, Stripe and Zapier named in the documentation index. Beyond the first party set there is a community integrations list with a Create Integration flow and per integration approval status, so third parties publish connectors others can adopt (Explorium documents its own onboarding through it).

Enterprise admins control which external services are available, manage shared versus app user credentials separately, and can block specific connectors across apps, Superagents and in app agents. Superagents themselves connect outward to third party applications and reach users over WhatsApp and Telegram. The Wix distribution adds Stores, Bookings, Blog, Events, Restaurants and CRM as context sources.

Sourcedocs.base44.com developer documentation, base44.com enterprise pages and Wix App Market listingread 2026-07-30

Every app Blink generates comes wired to a Turso database, Blink Auth sign in, file storage and a live web address with SSL. Beyond that core, 63 connectors across email, calendars, team chat, CRM, projects, payments, analytics and social media are connected once by a workspace admin, most with a single sign in, and each project then picks which accounts it may use.

When a builder describes an app, the agent checks which connectors are live and writes the code that reads and sends data through them, and every call is routed through Blink's connector service so no token sits in the app's code. A few tools, among them Meta Ads, ElevenLabs, Perplexity and Firecrawl, take a pasted key instead. Claw agents reach Notion, Google Drive, HubSpot and Slack and send email, and outside assistants can list, authorize and disconnect connectors through Blink's MCP server.

Sourceblink.new/integrationsread 2026-10-09

A Superagent splits a complex request into independent sub-agent tasks that run in parallel in the background, shows each in a task panel, lets the user stop the work while keeping finished results, and combines the outputs into one response. Superagent workflows are built from a chat description into scheduled or triggered multi-step runs managed from a Workflows page, and app workflows automate multi-step work on schedules, data changes or connector events.

Sourcedocs.base44.com/superagents/subagents and setting-up-workflowsread 2026-09-29

The build agent runs one multi step loop per request. It plans the change, writes the frontend and backend, sets up the database and sign in, lints and builds the app, and saves a version when the task is done.

An outside assistant can start the same loop through the blink_build_prompt tool, follow it with status and wait calls, and answer the agent when it stops on a question, since a new prompt is refused until that question is answered or the build is stopped.

Claw agents each run alone on their own machine and can be paused, resized or deleted without touching the others, so several can work in parallel, though they do not hand work to one another or share a plan.

Sourceblink.new/docs/cloud/tools/claude-connectorread 2026-10-09

Superagent workflows run on a schedule, such as every morning or every Monday, or when a trigger happens, such as an email arriving in a connected Gmail account or a change to the agent's data, with Run Now, pause, archive and automatic pausing of repeatedly failing scheduled workflows; app workflows additionally react to data changes, publishes and payments. Superagents are reachable in Base44 chat and over WhatsApp (including groups), Telegram, iMessage, Slack channels with an agent handle, LINE and a Chrome extension, and a message sent on a channel mid-task joins the work in progress.

Sourcedocs.base44.com/superagents/setting-up-workflows and customizing-your-superagentread 2026-09-29

Blink Claw agents run around the clock on a private cloud machine and act on their own schedule, with examples such as a 6:45 AM summary, a 3am inbox check and a Friday report, and on events, such as a follow up sent within ten minutes of a signup.

They take messages from Slack, Telegram and Discord, with WhatsApp also listed in the automation docs, can be chatted with inside Blink, and message the user first when something needs attention. How a schedule is set up is unclear.

The app builder itself starts work when someone sends a prompt, in the Blink workspace or from Claude, Claude Code or ChatGPT over MCP.

Sourceblink.new/clawread 2026-10-09

Agents are grounded in the application's own data entities, with AI assistants defined with custom tools and data permissions, and each entity supporting granular create, read, update and delete permissions. On the Wix surface, agents answer using the merchant's live site data. Superagents additionally reach connected business systems. No document ingestion, embedding or vector store, retrieval augmented generation, knowledge base object or citation of sources is described.

Sourcedocs.base44.com developer documentation and Wix App Market listingread 2026-07-30

Each build works from the project itself: its source tree, database schema, backend functions and saved versions. Blink's MCP server exposes the same material to outside assistants for reading, including file contents, the schema and a diff between any two versions, while secret files such as .env are never returned. Claw agents draw on the workspaces they are connected to, such as Notion and Google Drive. The Knowledge Base in Blink's docs is a retrieval feature for the apps Blink builds, so the build agent keeps no searchable index of a company's wider documents.

Sourceblink.new/docs/cloud/tools/claude-connectorread 2026-10-09

The owner turns Superagent memory on or off and scopes it as separated, remembering facts and history within each conversation, or shared, remembering across all conversations so what the agent learns in one is available everywhere. Under Personalization the user can review what the Superagent has learned about them and delete memories they no longer want it to use, and the agent can change how it uses memory when the owner asks in chat. No retention period is stated.

Sourcedocs.base44.com/superagents/customizing-your-superagentread 2026-09-29

Claw agents keep 1 GB of storage and memory that survives restarts, so preferences, goals and context carry from one conversation to the next, and pausing an agent stops its machine while keeping its data. How that memory is stored, reviewed or cleared is unclear. In the app builder, continuity comes from the project rather than from the agent: every finished task saves a version with a screenshot and a generated description, and the agent rereads the project's code and schema on each request instead of carrying memory of its own across projects.

Sourceblink.new/clawread 2026-10-09

Before a Superagent sends a change to an app it asks for the owner's approval and names the app it is about to change, it asks for approval before installing a skill (answerable Yes or No in WhatsApp), and other actions that need approval are handled in the Superagent in Base44. Security settings carry per-agent permission toggles, with Update data and Delete data advised only when the role needs them; interactive actions run under the chatting user's own permissions; and enterprise admins can block connectors and disable Superagents across the whole workspace.

Sourcedocs.base44.com/superagents/customizing-your-superagent and enterprise documentationread 2026-09-29

Plan mode lets a builder think a change through with the agent, which only analyzes and replies and does not run tools, write files or deploy, and moving from Plan to Agent asks for confirmation before implementation starts. Agent mode then makes the changes.

Production stays apart from the work: each finished task updates a private preview and saves a version, the live app changes only when someone clicks Publish, and any earlier version can be restored and republished. Outside assistants change code only through a full Blink agent turn, since the MCP server has no file write tool, and a viewer's connection is read only. Claw agents act on their own, with the secrets vault setting what each one can reach.

Sourceblink.new/docs/reference/modesread 2026-10-09

Base44's trust center at base44.com/security lists SOC 2 Type II and ISO 27001, plus GDPR. Data is protected by TLS 1.2+ in transit and AES-256 at rest, with secrets held in cloud KMS, and the program includes OWASP-based penetration testing, threat modeling, secure design and code review. There is also an active bug bounty program and a third-party vendor risk program covering every supplier.

SSO through the organization's own IdP is enforced across the workspace and every app inside it, alongside SCIM provisioning with automatic joiner and leaver sync, OAuth 2.0 connectors, IP allowlisting by address, range and subnet, and domain-based access control. Enterprise workspaces are opted out of model training by default. Two-way GitHub export lets a customer run their own security and compliance scanners over the generated code. The platform runs on Wix's enterprise security infrastructure.

Sourcebase44.com/security trust center and base44.com/enterpriseread 2026-07-30

SOC 2 is in progress and not yet complete. The DPA sets out TLS 1.2 or higher with HSTS in transit and AES 256 or equivalent encryption at rest, and, for the company's own production systems, role based access, single sign on, mandatory multi factor authentication, central application and access logs and audit logging on privileged operations, with breach notice within 72 hours.

Inside a project, one Owner controls visibility, Admins and deletion, Admins edit with the AI, invite people and publish, and Users can only view. Both roles can be invited on every plan, Free included, with no cap on numbers, and Business adds access levels set per project. None of the plans lists single sign on for logging in to Blink.

Sourceblink.new/dparead 2026-10-09

Every Superagent workflow run is recorded, with an Activity tab listing each run's date, workflow, status and duration and per-workflow run history, success rate and average runtime, and the agent can be asked in chat what happened in a run; sub-agent tasks are shown in a task panel.

An app Logs page records user activity and function calls through to schema and integration changes, an Audit Logs API offers filterable event types, and a Monitoring API with a workspace owned key serves enterprise admins. The app Logs page is described only briefly, and the Superagent run record shows each run's status without listing the actions taken.

Sourcedocs.base44.com setting-up-workflows, llms.txt index and enterprise documentationread 2026-09-29

Every finished task saves a version with a screenshot, a generated description of the change, a timestamp and, for projects connected to GitHub, a commit SHA, so a builder can see what the agent changed and when a problem first appeared, then restore a working state. Outside assistants can read the version list, the source tree and a diff between versions over MCP.

For apps with a Blink Backend, the Backend tab shows every request live with its route, status code, response time and any error, and function logs can be pulled over MCP. Whether the build agent's individual tool calls are kept as a trace, or a workspace keeps an audit log of agent activity, is unclear.

Sourceblink.new/docs/launch/publishread 2026-10-09

Enterprise workspaces can choose where workspace app data is stored, across the US, EU or UK, to meet data sovereignty and compliance requirements, and applications are hosted on continuously monitored private infrastructure. No on-premises, air-gapped, customer VPC or self-hosted deployment is offered, and the platform runs as SaaS on Wix infrastructure. Two-way GitHub sync exports the full source code to the customer's repository.

Sourcedocs.base44.com enterprise documentation and base44.com pricing FAQread 2026-09-29

Core platform data, app databases on Turso, sign in and the build sandboxes sit in the United States on a hosted service. API servers run in the US, the Netherlands and Singapore with requests handled by the nearest one, and Claw agent machines run on Fly.io in US cities, Amsterdam, Frankfurt or London, with each agent's data stored where it runs. Customers do not pick a region.

The way off the platform is the code: web apps are standard React and TypeScript on Vite and mobile apps are React Native with Expo, a code download costs 5 credits on Starter and Pro and nothing on Max, and projects sync both ways with GitHub, with the agent's own Git operations coming on Pro, so the code can be taken elsewhere.

Sourceblink.new/dparead 2026-10-09

A template marketplace at base44.com/templates offers more than one hundred ready-made app templates and design layouts built by the Base44 community, with category pages including community and creative tools, and users pick a template, customize it with AI and launch.

Base44 suggests browsing the templates, finding one that shares similar workflows, cloning it and asking Base44 to modify it, with a worked example of reusing a project management template's task assignment flow for an event app. Skills are packaged reusable units, with up to ten attachable per agent and workspace skills shared across the workspace alongside app-level skills. These are app templates and reusable skills, and no prebuilt Superagents are offered, so agents are created by generation.

Sourcebase44.com/templates and category pages, base44.com blog, docs.base44.com AI agents documentationread 2026-08-31

Blink Claw ships four named agents, each with its own role, instructions and recommended model. Gerald works as a chief financial officer on financial models, books and taxes, and Jamie as an executive assistant on morning briefings, tasks and email drafts.

Alex researches prospects and handles outreach and follow ups as a sales development rep, and Maya triages an inbox and drafts replies.

For apps, step by step tutorials walk through building a CRM, an analytics dashboard, a project manager, an online store, a course platform and several AI tools, and any public project can be remixed as a starting point.

Sourceblink.new/clawread 2026-10-09

Users select the model that powers each agent under an AI Model setting, keeping Automatic for fast cost-effective responses or choosing a model from Google Gemini, OpenAI GPT or Anthropic Claude for more advanced reasoning, with the setting applied per agent and switchable at any time.

Credit consumption is published per model tier, naming the Automatic default as based on Gemini 3.1 Flash Lite at approximately three credits per message, Gemini 3 Flash at a moderate increase, and higher-end models such as GPT-5.6 Sol for complex analysis.

Users on Base44's public feedback forum report that model selection was removed from the builder chat used for coding, which is separate from the agent setting.

Sourcedocs.base44.com AI agents for apps documentationread 2026-08-31

Auto, the recommended setting, routes simple interface changes to fast models, complex features to advanced ones, debugging to reasoning models and design work to models that read images.

A builder can switch Auto off and pick the build agent's model directly from Google (Gemini 3 Pro and Flash), OpenAI (GPT-5.2 and GPT-5.1), Anthropic (Claude Opus, Sonnet and Haiku 4.5), xAI (Grok Code Fast) and Z.ai (GLM 4.6), with advanced models included from the Pro plan and costing more credits per request.

Claw agents choose separately from 13 models, Claude Sonnet 4.6 by default alongside GPT-5.4, Gemini 3.1 Pro, DeepSeek, Kimi and GLM, and can switch at any time. The AI Gateway's models serve the apps Blink builds rather than the builder.

Sourceblink.new/docs/reference/modelsread 2026-10-09

Base44's developer platform includes a CLI (including agents and agent-skills pull and push), a typed SDK with an agents interface, backend functions, automations, an Apps API, Enterprise APIs, an Audit Logs API and a Monitoring API, personal access tokens, App MCP letting assistants such as Claude, ChatGPT and Cursor work with a published app's data, agents and tools, a documentation MCP and llms.txt index, and bring-your-own coding agent into the app editor.

Superagents can be reached with a personal access token. Two-way GitHub sync now exports the full source code, where it once covered only the frontend.

Sourcedocs.base44.com/llms.txt and base44.com/pricingread 2026-09-29

A remote MCP server at blink.new/mcp, signed in with OAuth and bound to one workspace, carries scopes for reading the workspace and projects, writing projects and running builds.

Its 37 tools cover projects, the database, backend logs, builds, source and versions, publishing, and skills and connectors, so an assistant can start a build, answer the agent's questions, roll back to an earlier version and publish, and setup is laid out for Claude, Claude Code and ChatGPT.

Billing, workspace deletion and ownership transfer stay out of reach, and adding secrets or switching models has to happen in the browser. Separately, the AI Gateway API, reached with workspace API keys, gives code chat completions, media generation, web search and file upload.

Sourceblink.new/docs/cloud/tools/claude-connectorread 2026-10-09

A real iteration loop exists for the app being built: generate, preview instantly on built in hosting, inspect, and refine either by prompting again or through a visual editor that allows direct click to change edits to layout, copy and styling, with real time collaboration and version control tracking changes. Two way GitHub export lets a team run their own external security tooling and specialized compliance scanners over the generated code.

Agents themselves get no evaluation tools, with no harness or sandbox for rehearsing a Superagent against test inputs before it runs live on schedules and real events, no automated scoring and no regression testing when a prompt or integration changes. Third party reviews report that debugging uses build credits without always resolving the problem.

Sourcedocs.base44.com, base44.com/security and third party platform reviewsread 2026-07-30

Each finished task runs a lint check and a build before the preview updates and a version is saved, and preview errors are surfaced to the agent and, over MCP, to outside assistants. When something breaks, the agent investigates in chat before changing code, and an earlier version can be restored. In mobile apps, features such as the camera, health data, push notifications and haptics only behave correctly on real hardware, so Blink points builders to testing on a phone through Expo Go. Whether the agent writes and runs its own tests for the app is unclear.

Sourceblink.new/docs/launch/publishread 2026-10-09

Superagents complete tasks on the web from chat with no setup, in a cloud browser shown in a Live Browser view the user can follow, expand or close while the agent keeps working, with browser actions and data extractions metered per action and failed actions free. Base44's own Superagent Chrome extension lets the agent open tabs, click, type and read pages in the user's own Chrome, in its own tab group under Chrome's control banner and with the user's signed-in sessions, and falls back to the cloud browser when Chrome is not connected. Private network addresses are blocked.

Sourcedocs.base44.com/superagents/browser-controlread 2026-09-29

Claw agents come with a web browser beside Python, Node.js and bash, and browsing is part of the jobs they take on, such as prospect research, morning briefings and inbox work. Whether they can click through pages, fill in forms or work inside sites that need a login is unclear. The app build agent works through code, its preview and the build tools rather than operating a browser or a desktop.

Sourceblink.new/clawread 2026-10-09