Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.readdy.ai/llms.txt

Use this file to discover all available pages before exploring further.

Readdy Backend is Readdy’s built-in backend foundation. It lets your project use a database and server-side functions directly inside Readdy, without first subscribing to and setting up a separate third-party backend service such as Supabase. It is designed to feel low-friction for non-technical users — in many cases, the connection and setup flow happens through Readdy with very little manual infrastructure work. Readdy Backend includes two core modules:
  • Database: manage and inspect your project’s data
  • Functions: run custom server-side logic for your project
With Readdy Backend, you can:
  • Skip separate backend setup: add backend capability to your project inside Readdy instead of first configuring a separate database service
  • Start simple and go deeper: begin from Readdy’s UI and Chat, then move into direct data tools only when you need more control
  • Choose your level of control: use visual tools for everyday work, and use SQL or Functions when your workflow becomes more advanced
  • Support real product scenarios: manage leads, forms, products, orders, internal data, automations, and custom server-side workflows
Prerequisites: Readdy Backend and Supabase cannot be connected to the same project at the same time. If your project already uses Supabase, disconnect it first before connecting Readdy Backend.
Disconnecting either Supabase or Readdy Backend from a project is a high-risk action. It may break existing features, cause function failures, or result in data loss on your website. If the project is already in use, make sure you understand the current setup and back up any important data before disconnecting.

​
Application Layer & Use Cases

Readdy Backend gives your project the core backend tools behind the scenes. But for many users, that does not mean working in Database or Functions every day. Readdy also offers simpler, task-focused tools for common business needs, so you can manage your work through pages that match what you are trying to do.
  • Use Database and Functions when you need direct backend access and control.
  • Use a Readdy application when you want a simpler workflow built for a specific job.
E-commerce users should usually start with Shop to manage products and orders, instead of manually editing product and order tables in the database. The backend is still powering that experience underneath, but the Shop workflow is easier, safer, and more intuitive for non-technical users. Use this rule of thumb:
  • If a Readdy application already exists for your use case, start there.
  • If you need direct data access, use Database.
  • If you need custom server-side logic, use Functions.
Use application modules (Shop) first when available. They are usually easier and safer for non-technical users.

​
Terminology

TermMeaning
DatabaseThe place where your project’s structured data is stored.
TableA collection of records, like a spreadsheet for one type of data.
RowOne record inside a table.
ColumnOne field inside a table, such as name, email, or price.
SchemaA grouping layer inside the database. In Readdy Backend, public is the main schema for app data.
Table EditorA visual way to browse and edit data without writing SQL.
SQL EditorA text editor for writing custom database queries.
FunctionA piece of server-side code you can deploy and run for custom backend logic.
Endpoint URLThe URL you can call to trigger a deployed function.
Application layerA higher-level Readdy module built on top of the backend foundation, such as Shop.

​
How to Connect

1

Open the Connects Panel

Click the Connects button in your project.
Open Connects Window
2

Find Readdy Backend

Locate Readdy Backend in the Connects panel.
Find Readdy Backend in the Connects panel
3

Click Connect

Click Connect. Readdy takes you back to the Editor and sends the setup request automatically.
4

Verify the Connection

When the connection is ready, Readdy Backend shows as Connected.
Backend is connected
You can also connect Readdy Backend through Chat. Describe your needs — for example, tell Readdy that you need backend storage for sign-up data, products, orders, leads, bookings, or any other feature that requires stored data.
Adding backend through Chat
Start from Chat when you are creating a new backend structure from scratch. Describe the outcome you want before jumping into tables.

​
Using Database

Database gives you two working modes: Table Editor and SQL Editor.
Table Editor view
SQL Editor view

​
How to Use It

  1. Open Backend in the sidebar, then open Database.
    Expand Backend and select Database
  2. Select a table from the left panel.
    Switch between tables
  3. Use Table Editor for most everyday actions.
  4. Switch to SQL Editor when you need a custom query.
    Run a query in SQL Editor
  5. If there are no tables yet, go to Chat and ask Readdy to create the data structure you need.

​
What You Can Do in Database

  • Search tables and switch between visible schemas
  • View table rows with pagination
  • Edit cells directly in Table Editor
  • Insert a row, edit a row, or delete a row
  • Add, edit, or delete columns
  • Use a picker for foreign-key fields
Review data carefully before deleting rows or columns, because this can affect page content or app behavior.

​
Table Editor vs SQL Editor

  • Choose Table Editor if you want a visual, low-risk workflow.
  • Choose SQL Editor if you need a custom query and you already understand SQL.

​
Using Functions

Functions lets you create and deploy custom backend endpoints for your project.
An example of adding a function

​
Why Use Functions

  • You need logic that should run on the server side instead of in the page.
  • You want an endpoint your project or an external service can call.
  • You need to handle custom workflows that go beyond simple data editing.

​
Common Scenarios

  • Handling webhook-style requests
  • Connecting with third-party services
  • Running custom processing logic
  • Building automation behind forms, orders, or internal tools
  • Creating backend endpoints for features that need more than UI-level logic

​
What You Can Do in Functions

  • View all deployed functions in one list
  • Search functions by name
  • Create a new function
  • Edit and redeploy an existing function
  • Copy a function URL
  • Delete functions you no longer need

​
How to Use It

  1. Open Backend in the sidebar, then open Functions.
  2. Click “Deploy a New Function”.
  3. Enter a function name (function name is mandatory).
  4. Write your code in the editor.
  5. Click “Deploy Function”.
  6. Copy the generated URL from the list when you need to call the function.
View Function list

​
Usage Limits and Out-of-Scope Cases

  • Database is not the best place for everyday business operations if a dedicated Readdy application already exists for your use case.
  • In SQL Editor, only one SQL statement can run at a time.
  • In SQL Editor, write operations are only allowed in the public schema. Other visible schemas are read-only.
  • Primary-key cells cannot be edited directly in Table Editor.
  • Some rows or columns may not be deletable if other data depends on them or if the table is protected.
  • Functions supports deploying and managing functions, but it is not a full backend operations suite. Items such as local debugging, logs/monitoring, migration management, and backup/restore are not part of this module.

​
Tips and Best Practices

Keep functions focused. One clear purpose per function is usually easier to manage than one large all-purpose function.
Use Database to verify what is really stored, especially when your UI is driven by dynamic data.

​
FAQ

That usually means your project does not have any tables yet. Go to Chat and describe what data you want to store, such as users, products, orders, forms, or leads.
Use Shop for normal e-commerce operations like managing products and orders. Use Database when you need direct access to the underlying records or when you are working with data outside the Shop workflow.
Direct cell editing only works when the table has a primary key. Primary-key fields themselves are not editable in the inline editor.
Check these common causes:
  • You tried to run more than one statement at once
  • You tried a blocked system-level operation
  • You tried to write outside the public schema
  • Your SQL has a syntax or table-name issue
The record may still be referenced by other data, or the table/column may be protected. Remove or update the dependent data first, then try again.
After deployment, the URL appears in the Functions list. You can copy it directly from there.

​
Need Help?

If this guide doesn’t resolve your issue, submit a support ticket. We’re here to help!