What is HeroMate?
Welcome to this tutorial series. We will walk from what HeroMate is to how you use it in your projects. This lesson explains HeroMate from a mostly non-technical angle so the big picture is clear before you touch code.
Frontend and backend
Most applications have two sides:
- Frontend — what users see and click. In recent years there has been a huge wave of AI-assisted tools (for example Lovable and similar) that help you ship interfaces very fast.
- Backend — the part users do not usually see, but it does the heavy work: database, authentication, APIs that read and write data, automations, email, integrations—anything that is not “just the screen.”
All of that does not happen in the visual layer alone.
Why HeroMate exists
There are many tools for pieces of the puzzle, but few give you the whole backend story in one place. HeroMate is built so you can stand up that invisible side more easily and focus on your frontend—especially now that editors like Cursor, Claude Code, and similar tools let your AI work next to your repo.
You connect the HeroMate MCP to your project. Then, while you or your AI build the UI, the assistant can hook into HeroMate and help create tables, endpoints, file uploads, user management, and more—without you having to become a backend specialist first.
Build in Studio (no external IDE)
If you'd rather not wire up an editor at all, Studio is the in-dashboard AI app builder and the default mode of every project. Describe what you want in a chat prompt, watch the live preview update as the app takes shape, then publish — all without leaving HeroMate. Studio is the fastest path for non-technical builders, and developers can switch to dev mode (editing the code) on the Pro plan.
HeroMate is also meant to lower the barrier for people who are not deeply technical, so they can ship simple applications end to end—while still being powerful for developers who want speed. Many teams use it even while the product evolves: it can save a lot of time because you move at a very high pace.
AI with no keys to manage
The AI that builds your backend runs on HeroMate Managed AI by default — there's no API key to bring, and usage is metered as AI Credits. You can still bring your own OpenAI, Anthropic, or Gemini key later (BYOK) when you want to pay a provider directly, but you don't need one to get started.
A backend that's already wired up
Your apps aren't limited to plain data and APIs. HeroMate ships 40 workflow nodes, including real integrations like Stripe, Telegram, WhatsApp, Slack, Notion, Google Sheets, GitHub, and Shopify — plus a generic HTTP Request node for anything else. You connect them as your app grows; no custom glue code required.
What makes HeroMate different
The most important idea: everything the AI generates for your backend—those flows—you can open and see inside HeroMate as a visual representation. As of today, that combination—AI-assisted creation plus a clear, visual view of what was built—is something other tools do not offer in the same way.
What you'll learn in this video
- Frontend vs backend in plain language
- Why HeroMate focuses on one place for the “invisible” work
- How MCP connects your IDE and AI to your HeroMate project
- Why seeing backend flows visually matters
Next
Continue to the platform overview, then the rest of the series will show examples and walk through creating a project together.