Frequently asked questions

Codata IO questions,
answered.

Setup, your coding agent, the cloud, each core service and pricing. 103 answers across 13 topics.

The agentic cloud

Codata IO in one answer

Codata IO is a cloud platform for apps built with AI coding agents. You build with the agent you already use, like Claude Code, Cursor or Copilot, and Codata IO sets up and runs the whole backend: database, logins, storage, hosting, domains, email, real-time, automated tasks, webhooks, AI model access and secrets. 12+ core services, one click to set up, one bill.

01

Getting started

What is Codata IO?

Codata IO is a cloud platform that runs the entire backend for apps built with AI coding agents, so you can take an app from preview to live without setting up or operating infrastructure.

You build with the coding agent you already use, like Claude Code, Cursor or GitHub Copilot. Codata IO sets up and runs everything underneath the app in one place:

  • Database, file storage and real-time updates
  • Logins and access rules
  • Hosting and domains
  • Email and user notifications
  • Automated tasks and webhooks
  • An AI model gateway and a runtime for your app's own AI agents
  • A secret manager for keys and credentials

That's 12+ core services on one platform and one bill. Your cloud is set up in a click, it adapts as your agent changes the app and it watches itself for you, so your time goes into the product instead of the infrastructure behind it.

Link to this answer

Who is Codata IO for?

Codata IO is for anyone who wants to build the product, not run the backend.

That includes solo founders and first-time builders shipping with an AI agent, product leaders turning an idea into a working app, and senior engineers, ML experts and R&D leaders who could run infrastructure but would rather spend their time on the product.

What they share isn't a skill level. It's the decision that designing databases, connecting services and operating servers is not where their time should go.

Link to this answer

Who is Codata IO not the right fit for?

If you want hands-on control of every server setting, or you need to self-host, Codata IO probably isn't the right fit.

Codata IO is a managed cloud. It decides how your backend is set up and runs it for you. Teams that want to tune their own infrastructure, run their own deploy pipelines or host the stack on their own hardware are better served by tools built for that, such as open source, self-hostable backends or a general-purpose cloud.

Link to this answer

How does Codata IO work?

You connect your coding agent to Codata IO, describe your app and build as usual. Codata IO sets up the backend the app needs and takes it live.

  1. Create a Codata IO account and a workspace. Your cloud is set up in a click.
  2. Connect your coding agent through the Codata IO MCP server: one command in Claude Code, or a short config in Cursor or VS Code.
  3. Build as usual. As your agent writes the app, Codata IO plans the data, logins, storage and other services behind it. Bigger changes, like access rules, come to you as a plan to approve.
  4. Go live. Your app gets a live address on a free Codata IO domain, and you can connect your own domain anytime.
  5. Keep building. As your agent changes the app, the backend keeps up.
Link to this answer

How long does it take to go live with Codata IO?

Codata IO is built to take an agent-built app live in minutes, not days.

There's no hosting account to open, no database provider to sign up for, no email vendor to connect and no deploy pipeline to configure. The backend is set up while your agent builds, so going live is one step at the end instead of a project of its own.

Link to this answer

Do I need to know about servers, databases or DevOps?

No. Codata IO handles the backend, so you don't need to design a database, configure servers or manage deploys.

You describe what the app should do, your agent builds it and Codata IO works out the infrastructure it needs and runs it.

If you do know your way around infrastructure, nothing is hidden from you. You can see what's running and ask Codata IO to explain any decision it made about your backend.

Link to this answer

Do I need a coding agent to use Codata IO?

No, but Codata IO is designed to work alongside one.

You can start an app inside the Codata IO app without an agent, then connect Claude Code, Cursor, Copilot or another agent whenever you're ready. The usual setup is to bring the agent you already use: the agent writes the app, and Codata IO runs everything it needs.

Link to this answer

What are Co-Live and Auto-Runtime?

They're Codata IO's two products. Co-Live takes your app from build to live as one motion. Auto-Runtime keeps it live and adapting as your agent changes it.

Every core service, from the database to email, is a feature within these two products. Co-Create, which takes you from idea to production, is coming soon.

Link to this answer
02

Vibe coding and AI apps

What is vibe coding, and where does Codata IO fit?

Vibe coding means building software by describing what you want to an AI coding agent, which writes the code for you. Codata IO is the cloud that runs what the agent builds.

The agent, such as Claude Code or Cursor, handles the code. What it can't do by itself is run a live backend: a database, logins, hosting and email. Codata IO sets that up and runs it, so a vibe-coded app becomes a live product.

Link to this answer

How do I vibe code an app and take it live?

Describe your app to a coding agent that's connected to Codata IO. The agent writes the app, Codata IO sets up the backend behind it and you go live on a real web address.

  1. Pick a coding agent, such as Claude Code, Cursor or GitHub Copilot.
  2. Connect it to Codata IO. It takes one command or a short config.
  3. Describe the app in plain language and let the agent build.
  4. Approve the plan when a bigger backend change comes up, like access rules.
  5. Go live on a free Codata IO domain, then connect your own domain when you're ready.
Link to this answer

Why do AI-built apps get stuck before launch?

Because the agent writes the app, but a live app also needs a backend that someone has to set up and run. That's the part an agent can't close by itself.

A preview on your laptop doesn't need real logins, a production database, hosting, a domain or email. A live app needs all of them, and each one usually means another service to choose, connect and watch. Codata IO closes that gap by running all of it as one cloud, set up in a click.

Link to this answer

Can a vibe-coded app handle real users?

Yes, when what's underneath it is built for production. On Codata IO, a vibe-coded app runs on a cloud that scales automatically and heals itself.

Logins, access rules and secrets are handled by the platform instead of being improvised in generated code. Capacity grows with your traffic, and the backend realigns as your agent keeps changing the app.

Link to this answer

Can I build a full SaaS product by vibe coding?

Yes. With a coding agent writing the app and Codata IO running the backend, you can build a product with user accounts, saved data, file uploads, email and live updates.

Built-in payments are coming soon. Today you can connect a payment provider like Stripe through webhooks.

Link to this answer

How much does it cost to run a vibe-coded app?

On Codata IO you can start at $0 on the Free plan. Running a real app starts at $25 a month plus usage on the Builder plan.

That one bill covers the whole backend: database, logins, storage, hosting, email and the rest. Your coding agent's subscription is separate and paid to its provider.

Link to this answer

Can I make money from an app I built with AI?

Yes. An app running on Codata IO is a real, live product with its own domain, logins and data, so you can sell it like any other.

Built-in payments are coming soon to Codata IO. Today you can connect a payment provider like Stripe through webhooks, so payment events land directly in your app's data.

Link to this answer

How do I keep an AI-built app secure?

Let the platform handle the sensitive parts instead of leaving them in generated code. On Codata IO, logins, access rules and secrets are built into the backend.

  • Logins come with email verification and password reset built in
  • Access rules are designed by Codata IO and applied through a plan you approve
  • API keys and passwords live in the secret manager, encrypted at rest and in transit, with nothing pasted into code
  • Your app and backend are versioned, so you can roll back a bad change
Link to this answer

What is a backend, and does my app need one?

The backend is everything your users don't see: where data is stored, how people log in and how files and email work. Any app with accounts or saved data needs one.

The frontend is the screens people use. Coding agents can write both, but a backend also has to be hosted, secured and kept running. Codata IO does that part for you.

Link to this answer

Can I build a mobile app on Codata IO?

Mobile app support is coming soon. Today, Codata IO runs web apps, AI apps, marketing sites, platforms and AI agents.

A web app on Codata IO opens in any phone browser, which is a practical way to launch while mobile app support is on the way.

Link to this answer

Can I use Codata IO if I can't code?

Yes. Your coding agent writes the code and Codata IO runs the backend, so you can go from idea to live app by describing what you want.

You can also start an app inside Codata IO without an agent. And if you can code, nothing changes. You just skip the infrastructure work.

Link to this answer

What's the best backend for an app built with AI?

The right backend for an AI-built app is one your agent can set up and change by itself, that covers everything the app needs and that you don't have to operate.

Five things to look for:

  • It connects to your coding agent through MCP
  • It covers database, logins, storage, hosting and email in one place
  • It keeps up when the agent rewrites the app
  • It scales and watches itself
  • It comes on one bill

Codata IO is built around those five points.

Link to this answer
03

Your agent and MCP

Which coding agents work with Codata IO?

Codata IO works with the coding agent you already use, including Claude Code, Cursor and GitHub Copilot in VS Code, plus other agents that support MCP.

MCP (Model Context Protocol) is the open standard coding agents use to connect to outside tools. Any agent that speaks it can connect to Codata IO.

Your backend lives in Codata IO, not in your editor, so you can change agents later and keep your app where it is.

Link to this answer

Does Codata IO replace my coding agent?

No. Your agent builds the app. Codata IO makes it real: it runs the backend and takes the app live.

Codata IO doesn't write your app's code or move you into its own builder. You keep your agent, your workflow and your project. Codata IO is the cloud underneath.

Link to this answer

Does Codata IO have an MCP server?

Yes. The Codata IO MCP server is live, hosted at https://mcp.codata.io/mcp and included on every plan, Free included.

Through it, your coding agent can set up and change your backend, read and change your app's data and take the app live, all from the same conversation you build in.

You sign in once, in your browser, the first time your agent uses it. Setup steps for each agent are in the MCP setup docs.

Link to this answer

How do I connect Claude Code to Codata IO?

Run one command in your terminal, then sign in to Codata IO in your browser the first time Claude Code uses it.

claude mcp add --transport http codata https://mcp.codata.io/mcp

After that, describe the app you want. Claude Code builds it, and Codata IO runs the backend underneath.

Link to this answer

How do I connect Cursor or VS Code with Copilot?

Add the Codata IO MCP server URL, https://mcp.codata.io/mcp, to your editor's MCP settings, or install the Codata for VS Code extension.

  • Cursor: add the URL to your MCP config file.
  • VS Code: add the server (or install the extension) and use Copilot Chat in Agent mode.

Sign-in happens in your browser on first use. Full steps are in the MCP setup docs.

Link to this answer

What can my coding agent do in Codata IO?

Your agent can set up and change everything your app needs to run, from the same conversation it builds in.

  • Plan and apply backend changes, like new kinds of data or access rules
  • Read and change your app's data
  • Set up logins, storage, email and automated tasks
  • Take the app live and connect a domain
  • Check your app's health and roll back a change
Link to this answer

Do I stay in control of what my agent changes?

Yes. Bigger backend changes, like access rules, come to you as a plan you approve before anything is applied.

Codata IO also keeps versions of your app and backend, so if a change doesn't work out you can roll back to an earlier version.

Link to this answer

What is an MCP server, and why does Codata IO use one?

An MCP server lets an AI coding agent use an outside tool. MCP (Model Context Protocol) is the open standard for it. The Codata IO MCP server is how your agent sets up and changes your backend.

Without it, an agent can write code and then hand you a list of setup steps. With it, the agent can create the database, set up logins and take the app live itself. The Codata IO MCP server is hosted, so there's nothing to install or run, and it's included on every plan.

Link to this answer

How do I deploy an app I built with Claude Code?

Connect Claude Code to Codata IO and ask it to take the app live. Codata IO hosts it and gives it a live address on a free Codata IO domain.

claude mcp add --transport http codata https://mcp.codata.io/mcp

There's no separate hosting account or deploy pipeline to set up. The same works from Cursor and from VS Code with Copilot.

Link to this answer

Which coding agent should I use with Codata IO?

Use the one you like. Codata IO works the same way with Claude Code, Cursor, GitHub Copilot and other agents that support MCP.

Each agent has its own strengths and pricing, and they change quickly. Because your backend lives in Codata IO, you can switch agents without moving your app.

Link to this answer

Do I pay for my coding agent through Codata IO?

No. Your coding agent, such as Claude Code or Cursor, is a separate subscription paid to its provider. Your Codata IO bill covers the cloud your app runs on.

Link to this answer

Can I use Codata IO with Lovable or Bolt?

Yes, for the backend. Apps built in Lovable or Bolt can connect to Codata IO for data, logins and the other core services. Hosting stays with the builder.

If you'd rather keep the agent and the project fully yours, you can also move the app to a coding agent like Claude Code and run everything, hosting included, on Codata IO.

Link to this answer
04

A cloud that works for you

Is Codata IO a cloud provider or a backend-as-a-service?

Codata IO is a cloud platform: your own cloud, set up in a click, with 12+ core services built in.

Backend-as-a-service tools give you building blocks to assemble, configure and watch yourself. Codata IO runs the whole backend for you. It chooses the setup your app needs, keeps it running and adapts it as the app changes.

Link to this answer

What does one-click cloud setup mean?

When you create a workspace, Codata IO sets up a full cloud environment for your app, with nothing to configure first.

There are no separate accounts for hosting, email or storage and no keys to copy between services. Your app gets a custom architecture from minute one, shaped to what it needs to run in the real world, and it grows from there.

Link to this answer

What does "a cloud that works for you" mean?

It means Codata IO is an agentic cloud: it adapts to your product, instead of your product adapting to the cloud.

As your agent adds features, Codata IO works out the infrastructure behind them, applies optimizations like indexes, scales with usage and watches the system for you. You see a working app. The work of running it happens on Codata IO's side.

Link to this answer

What happens to the backend when my agent changes the app?

It keeps up. When your agent rewrites part of the app, Codata IO realigns the data, access rules and services behind it, so the next change doesn't break what's live.

Changes to how your data is structured are planned and applied for you, with no scripts to write or run. Keeping a fast-changing, agent-built app live and consistent is the job of Auto-Runtime.

Link to this answer

Is Codata IO self-healing?

Yes. Codata IO's infrastructure is self-healing: problems are resolved the millisecond they occur, so you stay focused on your product.

Codata IO watches your backend continuously, so you don't need to set up your own monitoring or be on call for the infrastructure.

Link to this answer

Does Codata IO scale automatically?

Yes. Codata IO scales at the cloud level, so capacity grows with your traffic and data without you planning it.

Your database, hosting and real-time connections all scale with usage. You never size servers in advance or babysit capacity during a launch, and because your cloud is sized to your product, you don't pay for capacity you don't need.

Link to this answer

Why use one platform instead of stitching separate tools together?

Because every tool you stitch together is another account, another bill and another place for things to fall out of sync.

On Codata IO, the database, logins, storage, email, hosting and the rest run on the same backend. Access rules are set once and apply everywhere. A scheduled task can read your data, attach a stored file and send an email in one motion, with no glue code between vendors. And it all comes on one bill.

Link to this answer

Is Codata IO open source? Can I self-host it?

No. Codata IO isn't open source and isn't self-hostable. It's a managed cloud that runs the backend for you, so there's nothing to install or operate.

Link to this answer

Who is behind Codata IO?

Codata IO was founded by a team with deep infrastructure experience in defense and banking, two fields where reliability isn't optional.

That background shapes the platform: a backend you don't have to watch, because it's built to watch itself.

Link to this answer
05

Data, storage and real-time

What database does Codata IO use?

Codata IO runs Postgres with vector search, plus other database types, chosen and set up for what your app needs.

You don't pick an engine or design tables by hand. As your agent builds, Codata IO plans how your data is structured, applies optimizations like indexes and partitions and scales the database with usage.

Link to this answer

Do I have to design the database myself?

No. Codata IO plans your data structure automatically as your agent builds and changes the app.

When the app needs a new field or a new type of record, the change is planned and applied for you. There are no change scripts to write or run, and the database stays aligned with the app even after many rewrites.

Link to this answer

Can I ask questions about my data in plain language?

Yes. Ask something like "which customers signed up this week?" and you get an answer, not a query to write.

Link to this answer

How does file storage work in Codata IO?

Codata IO Storage keeps your app's files in one place, connected to the rest of your data: images, documents, uploads and any other file type.

Files are available to the rest of your backend the same way your database is, with no separate access layer to set up. That means your app can store a file, filter it or email it in one motion, for example "send my photos folder to these recipients".

Link to this answer

Does Codata IO support real-time features?

Yes. Real-time is built in: when someone edits a record, every open screen can show it that second.

  • Live dashboards and activity feeds
  • Chat and broadcast channels
  • Presence, like "who's online right now", and live cursors

Real-time runs on the same data layer as your database and scales as connected users grow, so there's no separate real-time vendor to add or keep in sync.

Link to this answer

Can I build a chat or a "who's online" feature?

Yes. Codata IO real-time includes presence and broadcast channels, which are what chat, live cursors and "who's online right now" are built on.

It runs on the same data layer as your database, so there's no separate real-time service to add.

Link to this answer

Can I build a dashboard that updates by itself?

Yes. Your app can subscribe to changes in your data and push them to every open screen the moment they happen.

Link to this answer

Can users upload files and images in my app?

Yes. Codata IO Storage takes any file type, and uploads are kept in one place and connected to the rest of your app's data.

Link to this answer

Can my app email a file it has stored?

Yes. Storage and email run on the same backend, so sending a stored file to a list of recipients is one action.

Link to this answer

What happens to my database as my app grows?

Codata IO scales the database with usage and applies optimizations like indexes and partitions for you.

You don't size a database in advance or tune it by hand later.

Link to this answer

Can my coding agent read and change my app's data?

Yes. Through the Codata IO MCP server, your agent can read and change your app's data, which helps when you're building, testing or fixing something.

Link to this answer
06

Logins and access

How do I add logins to my app?

Logins are built into Codata IO. Sign-up, sign-in and password reset work from the first minute your app is live, with nothing to build.

Users can sign in with email and password or with Google. Email verification and password reset are built in, and there's no separate auth provider to set up or pay for.

Link to this answer

How are access rules set in Codata IO?

Your agent describes the access it wants, and Codata IO designs and applies the rules through a plan you approve. You can also write the rules yourself.

Because logins run on the same backend as your data and files, who can see what is defined once and stays consistent everywhere, instead of being set up separately for every feature.

Link to this answer

Do I need to find and copy keys like a service role key?

No. Your coding agent connects to Codata IO with a one-time sign-in in your browser, so there's no project URL, anon key or service role key to hunt for and paste.

Keys for outside services, like a payment or AI provider, go in the secret manager, and your app pulls them at runtime.

Link to this answer

Do I have to write row-level security (RLS) rules?

No. Your agent describes who should see what, and Codata IO designs the access rules and applies them through a plan you approve.

If you'd rather write the rules yourself, you can.

Link to this answer

How does Codata IO handle API keys and secrets?

Codata IO includes a secret manager: a central vault for API keys, passwords and tokens that your app pulls safely at runtime, with nothing pasted into code.

  • Encrypted at rest and in transit
  • Access control for which apps and users can read which secrets
  • Versioning, so you can roll back a bad update or pin a safe version
  • Auditing of who accessed a secret and when
Link to this answer

Can users sign in with Google?

Yes. Codata IO logins support Google sign-in as well as email and password.

Link to this answer

Do password reset and email verification work out of the box?

Yes. Both are built in and work from the first minute your app is live, with the emails sent from your app's domain.

Link to this answer

Can I see who accessed a secret and when?

Yes. The Codata IO secret manager keeps an audit record of who accessed each secret and when.

Link to this answer

Can I undo a bad change to an API key?

Yes. Secrets are versioned, so you can roll back a bad update or pin your app to a version you know is safe.

Link to this answer
07

Hosting and domains

Does Codata IO host my app?

Yes. Hosting is part of Codata IO: your app goes live on the web in the same motion as building it, with no deploy pipeline to manage.

When your agent ships a change, Codata IO takes it live. Hosting scales with traffic and stays aligned with the backend, so a new feature and the infrastructure behind it ship together.

Link to this answer

Can I use my own domain?

Yes. Every app gets a free Codata IO domain when it goes live, and you can connect your own domain, which Codata IO connects and manages for you.

Link to this answer

Can I roll back a change that broke something?

Yes. Codata IO keeps versions of your app and backend, so you can roll back to an earlier version when a change doesn't work out.

Link to this answer

Can I test changes before they go live?

Yes, with branches on the Pro plan. A branch is a separate copy of your workspace where you can try a change, preview it and merge it when it's ready.

Link to this answer

What kinds of apps can I run on Codata IO?

Web apps, AI-powered apps, marketing sites with working forms, multi-customer platforms and AI agents all run on Codata IO.

Support for mobile apps is coming soon.

Link to this answer

Can I host a marketing site with a working waitlist form?

Yes. Codata IO hosts the site and runs the form behind it, so sign-ups are saved to your data without a separate form tool or server.

Because email runs on the same backend, a new sign-up can also trigger a confirmation email.

Link to this answer

Do I need to redeploy every time my agent changes the app?

No. Your app goes live automatically as your agent builds and updates it. There's no deploy pipeline to run.

If a change doesn't work out, you can roll back to an earlier version.

Link to this answer
08

Email and notifications

Can my app send email with Codata IO?

Yes. Codata IO includes its own email server, so your app sends sign-up confirmations, password resets, receipts and product emails without a separate email provider.

  • Native access to your app's data, so an order can trigger a receipt the moment it lands
  • Emails like sign-up confirmations are sent from your app's domain
  • Built-in system accounts like no-reply
  • Plain text and HTML emails

There's no email vendor account to open and no extra bill to track.

Link to this answer

Can my app send notifications to its users?

Yes. User notifications are one of Codata IO's core services and run on the same backend as your data and email.

Link to this answer

Can my app send a receipt the moment an order comes in?

Yes. Email on Codata IO has native access to your app's data, so a new order can trigger a receipt right away, with no email vendor in between.

The same goes for any event in your data: a booking confirmation, a status update or a welcome email when someone signs up.

Link to this answer

Can my app send from a no-reply address?

Yes. System accounts like no-reply are built in, and emails go out from your app's own domain.

Every app gets a free Codata IO domain when it goes live, so there's no sending domain to set up before your first email.

Link to this answer

Can I email all my users at once?

Yes. Your app can send to one person or to many, so product updates and announcements go out from the same place as receipts and password resets.

Emails can be plain text or HTML.

Link to this answer
09

Automation and integrations

Can I run scheduled or background tasks?

Yes. Codata IO automated tasks run actions on a schedule (daily, weekly or a custom interval) or when something changes in your data.

Tasks are connected to your data, storage and email, so one task can reach across the whole app. For example: email a weekly report built from your data, send a file stored in Codata IO or email the content of a website on a schedule.

Link to this answer

Does Codata IO have serverless functions?

Codata IO uses Jobs instead of serverless functions: backend logic that runs on Codata IO's cloud on a schedule, on a trigger or on demand.

Jobs run next to your data, storage and email, so there's no separate functions platform to deploy to or connect.

Link to this answer

Does Codata IO support webhooks?

Yes. Your app can receive events from outside services like Stripe or Slack and send events out when something happens in the app.

  • Incoming requests are verified before they reach your app's logic
  • Failed deliveries are retried and logged, so an event isn't silently lost
  • Outgoing webhooks fire on a new record, a user action or a status change
Link to this answer

Does Codata IO handle payments?

Not yet. Built-in payments are coming soon to Codata IO.

Today, you can connect a payment provider like Stripe through webhooks, so payment events land directly in your app's data.

Link to this answer

Can a task run when my data changes?

Yes. Automated tasks can be triggered by a change in your data as well as by a schedule.

For example, a new record can kick off an email, a file action or a call to another service.

Link to this answer

Can I send a weekly report by email automatically?

Yes. Set a task on a weekly schedule, and it can build the report from your data and email it, all inside Codata IO.

Link to this answer

What happens if a webhook delivery fails?

Codata IO retries failed deliveries and logs them, so an event isn't silently lost.

Link to this answer

Can my app notify another service when something happens?

Yes. Outgoing webhooks can fire when a new record is created, a user takes an action or a status changes.

Link to this answer
10

AI inside your app

Can I run AI agents inside my app?

Yes. Codata IO includes a runtime for the AI agents your product runs, like support bots, in-app assistants and workflow agents. These are your app's agents, not the coding agent that builds it.

  • Agents read and write your app's data with permissioned access, scoped to only what they should see
  • Agents call tools and take action
  • Conversation memory and per-user sessions are built in
  • Every run is tracked and inspectable
  • Agents scale with usage, with no separate agent-hosting stack
Link to this answer

What is the Codata IO Model Gateway?

The Model Gateway is one managed gateway for every AI model call your app makes: a single integration instead of a separate one per provider.

  • No provider keys stored inside your app; credentials are secured centrally
  • Swap or add a model without changing your app's code
  • Usage, cost and latency for every model call in one place
Link to this answer

Can I run a support bot that reads real orders?

Yes. Codata IO's agent runtime lets you run a support agent that reads real orders and answers real customers, scoped to only the data it should see.

This is an agent your product runs for its users. It's separate from the coding agent you build with.

Link to this answer

Can I switch AI models without changing my app?

Yes. Your app calls models through the Model Gateway, so you can swap or add a model without touching the app's code.

Provider credentials are handled centrally, so there are no provider keys stored inside the app.

Link to this answer

Can I see what my AI calls cost?

Yes. The Model Gateway shows usage, cost and latency for every model call your app makes, in one place.

Link to this answer

Do AI agents in my app remember past conversations?

Yes. Conversation memory and per-user sessions are built into the agent runtime.

Link to this answer

Can I control what data an AI agent in my app can see?

Yes. Agents get permissioned access, scoped to only the data and actions they should have.

Link to this answer

Can I see what an AI agent in my app did?

Yes. Every agent run is tracked and can be inspected, so a run is never a black box.

Link to this answer
11

Plans and pricing

How much does Codata IO cost?

Codata IO has three plans: Free at $0 a month, Builder at $25 a month plus usage and Pro at $100 a month plus usage.

Every plan covers the whole platform on one bill. Pricing is usage-based, so you pay only for what your app actually uses. See pricing for full details.

Link to this answer

What's included in the Codata IO Free plan?

Free costs $0 a month and is a trial space for a real app: 1 workspace, 100 MB disk, 1 GB storage, 5 GB egress and 100K API calls.

If you reach a cap, metered usage pauses. Nothing is deleted, and you can pick up where you left off on a paid plan. The MCP server is included on Free too.

Link to this answer

What do the Builder and Pro plans include?

Builder ($25 a month plus usage) is for running real apps. Pro ($100 a month plus usage) adds more room and branches.

BuilderPro
Workspaces310, branches included
Disk5 GB each50 GB each
Storage100 GB1 TB
Egress250 GB500 GB
API calls1M10M
Link to this answer

What does "plus usage" mean?

Your plan price includes a monthly allowance. Beyond it, you pay for what your app actually uses.

Your cloud is sized to your product, so you never pay for capacity you don't need, and everything appears on one bill.

Link to this answer
12

Moving to Codata IO

Can I move my app from Supabase or Firebase to Codata IO?

Yes. Your coding agent, like Claude Code, can move your data and users to Codata IO for you.

Connect your agent to Codata IO, point it at your existing project and ask it to move over. The steps are in the import and migration guide.

Link to this answer

I already built an app with an AI agent. Can I bring it to Codata IO?

Yes. Connect your coding agent to Codata IO from the app's project, and it can work out what the app needs and move its backend over.

Once it's on Codata IO, the app goes live like any other, and the backend keeps up as your agent keeps building.

Link to this answer
13

How Codata IO compares

How is Codata IO different from Supabase?

Supabase gives you a strong set of backend tools to assemble and run yourself. Codata IO runs the whole backend for you.

Supabase is a good fit if you want open source, direct Postgres control or self-hosting. Codata IO is a cloud platform that brings 12+ core services together, including hosting, email and an AI model gateway, sets them up for your app and watches them for you, so you get a live app without operating the pieces.

Link to this answer

Is Codata IO a Supabase alternative?

Yes, for builders who want the backend run for them. Codata IO covers what people use Supabase for (a Postgres database, logins, storage and real-time) and adds hosting, email, automated tasks and an AI model gateway on the same platform.

Supabase is the stronger fit if you want open source or self-hosting. If you're switching, your coding agent can move your data and users over. The steps are in the import and migration guide.

Link to this answer

Is Codata IO cheaper than Supabase or Firebase?

The starting prices are similar: Codata IO and Supabase both have a $0 plan and a paid plan from $25 a month, and Firebase has a free tier and charges by usage. The difference is what the bill covers.

Codata IO's bill includes hosting, email and the rest of the backend, which often come from separate providers when you assemble a stack yourself. Your total depends on your usage, so compare against your own app.

Link to this answer

How is Codata IO different from Firebase?

Firebase is a mature platform from Google with strong mobile tooling. Codata IO is a cloud built for apps created with AI coding agents.

Codata IO runs Postgres with vector search, logins, hosting, email and the rest of the backend as one cloud that adapts as your agent rewrites the app, on one bill.

Link to this answer

How is Codata IO different from Vercel?

Vercel is excellent at hosting and deploying frontends, with a large ecosystem of integrations. Codata IO covers hosting and the whole backend behind it.

On Codata IO, the database, logins, storage, email, automated tasks and more run on one platform and one bill, instead of as separate integrations you connect and manage.

Link to this answer

How is Codata IO different from Lovable, Bolt or Replit?

Those are app builders with their own built-in agents, and they're a fast way to get a first version. Codata IO isn't a builder.

With Codata IO you keep the coding agent you choose and your project stays yours, while Codata IO runs the backend underneath and takes the app live.

Link to this answer

How is Codata IO different from AWS or Google Cloud?

AWS and Google Cloud offer a huge range of building blocks and suit teams with dedicated infrastructure engineers. Codata IO is a cloud built for agent-built apps.

Instead of choosing and configuring services, you get a complete backend set up in a click, shaped to your product and run for you. Skip the cloud learning curve and spend the time on the product.

Link to this answer

No answer for that yet

Try another word, or ask the Codata IO team.

Still curious

Still have a question?

Read the docs, talk to the team or bring your agent and take your app live.