Backend

The Backend area is where you manage the data and server-side logic that support an ioLoop Project. It has two main sections: Database, which stores structured application data and controls access to it, and Cloud Flow, which implements trusted server-side processing.

Backend functionality works with Pages, Forms, Widgets, Page Flow, custom frontend JavaScript, AI Agents, and Integrations. Depending on the requirement, you can use ioLoop's visual tools, supported APIs, custom code, AI Wiz, or a combination of them.

Backend Sections

Section	Purpose	Start Here When You Need To
Database	Define tables, fields, access rules, named queries, and application records.	Store data, manage its structure and permissions, or inspect development and production records.
Cloud Flow	Create server-side workflows, Web Hooks, Background Tasks, and shared backend functionality.	Enforce trusted business rules, call protected services, process files, or perform work on the server.

Database and Cloud Flow can be used independently or together. A simple application might rely primarily on permitted Database operations. A more complex application might use Cloud Flow to validate requests, coordinate multiple operations, and work with external services.

The detailed guides for each section explain how to configure these capabilities. For exact block inputs and API signatures, use the Backend Programming Guide.

Database

Database provides the Project's structured data model. Tables contain records, fields define the stored values, access rules govern permitted operations, and named queries provide reusable data retrieval patterns.

Examples of Project data include customers, orders, registrations, events, tasks, content records, and files associated with records.

Database can be used by:

• Table-Backed Forms for record creation and editing.
• Data Table Widgets and Data Design for data-driven displays.
• Page Flow and custom frontend JavaScript through supported Client APIs.
• Cloud Flow through supported server-side Database operations.
• AI Agents and other Project capabilities where configured.

Not every data operation requires Cloud Flow. Frontend code and built-in components can perform supported operations directly when the applicable Database access rules permit them.

For table creation, field configuration, permissions, queries, file fields, and data inspection, start with Database.

Cloud Flow

Cloud Flow is the server-side logic environment for a Project. Use it when functionality requires a trusted execution environment, protected credentials, centrally enforced rules, or processing that should not depend on an active browser session.

Cloud Flow supports Web Hooks for request-driven processing and Background Tasks for backend work that is not exposed as a Web Hook. It can use visual blocks, custom JavaScript in the supported Node.js runtime, ioLoop Server APIs, configured Connections, and shared backend helpers through Flow Share.

Typical uses include checking authorization before changing records, enforcing registration limits, calling an external service with private credentials, processing files, and returning controlled results to a Page or another caller.

For workflow types, creating and managing modules, the editor, security, testing, runtime behavior, and shared logic, start with Cloud Flow.

How Backend Works with the Frontend

The frontend manages the user experience. The Backend stores data and performs operations that require server-side trust.

Requirement	Typical Approach
Display or update permitted records	Use a Form, Widget, Page Flow block, or custom frontend JavaScript through the ioLoop Client APIs.
Retrieve a reusable set of records	Use a Database named query where appropriate.
Validate input for immediate user feedback	Use Page Flow or custom frontend JavaScript.
Enforce a protected business rule	Use Database access rules and trusted Cloud Flow processing as appropriate.
Call a service that requires private credentials	Use Cloud Flow with a configured Connection.
Process a request sent from a Page or external system	Use a Cloud Flow Web Hook.
Perform backend work independently of a Page	Use a supported Cloud Flow Background Task.

Forms, Widgets, and Page Flow blocks are higher-level implementations built on ioLoop Client APIs. A fully custom frontend using HTML, CSS, JavaScript, and those same Client APIs can implement equivalent behavior. The choice is about development approach and control, not exclusive access to underlying functionality.

Regardless of the frontend approach, Database permissions and trusted Backend authorization still apply. Hiding an element or validating a value in the browser is not a substitute for protecting the underlying operation.

Example: Event Registration

Consider an application where visitors register for events and administrators manage registrations.

1. Database: Create Events and Registrations tables, define the required fields, and configure access rules.
2. Frontend: Display event details and collect registration information using an ioLoop Form or a custom interface built with the Client APIs.
3. Cloud Flow: If capacity or eligibility must be enforced centrally, validate the request on the server before accepting the registration.
4. Integrations: Where needed, use configured Connections for confirmation emails, payments, or other external operations.
5. Result: Return the outcome so Page Flow or custom JavaScript can show confirmation, errors, or updated registration details.

This example shows how the pieces work together without requiring every frontend Database interaction to pass through a custom Cloud Flow workflow.

Development, Testing, and Publishing

ioLoop distinguishes development data from production data used by the published Project.

During Preview, built-in Database operations automatically use the development database. This allows record-oriented workflows to be tested without those operations modifying production records. Publishing Project changes does not mean development records are copied into production data.

External services and other custom or Cloud Flow behavior may have additional environment considerations. Check the relevant Connection, runtime, and operation before assuming that a test cannot have external effects.

For details, see Development and Production Data, Previewing, and Publish Project.

Working with AI Wiz

AI Wiz can help create or revise Database tables, named queries, Cloud Flow logic, and related Project functionality.

Describe the data, intended users, permitted operations, and rules the feature must enforce. Review AI-assisted changes in the corresponding Project Editor tools and test them before publishing.

Where to Go Next

Topic	What You Will Learn
Database	Manage the data model, permissions, queries, files associated with records, and development or production data.
Cloud Flow	Build and manage server-side workflows, Web Hooks, Background Tasks, shared code, and Connections.
Backend Programming Guide	Find the server-side programming references.
Cloud Flow Blocks	Look up exact block behavior and inputs.
Server API	Look up supported server-side APIs and signatures.

The Backend provides both straightforward data management and trusted processing for more complex workflows. Start with the simplest capability that meets the application's requirements, and add server-side logic where it is needed.