Developers · Build with AI
What Insites Can Do
Last updated 18 November 2026
A capability list: sign-in, roles, pages and JSON endpoints, data, email, files, languages, security, deploying and AI, with links.
This page lists what Insites can do, area by area. Each row says one of two things:
- Yes: Insites has it as a single tag, setting, file type or command.
- Built from parts: there is no single switch, but you build it from parts Insites has, such as a table, a query, a page and an email. The linked page shows how.
Moving an existing site? Start with Migrating to Insites.
Sign-In and Accounts
| Capability | Answer | How |
|---|---|---|
| Users with a sign-up form and a password | Yes | Creating a Sign-Up Form |
Sign a person in from your own code, with a session time limit (the sign_in tag with timeout_in_minutes) | Yes | Signing In a User Manually |
| Sign-in by emailed link, with no password | Built from parts: a short-lived token, a random value stored in a table, an email, and the sign_in tag | Passwordless Sign-In |
| Sign-in by an emailed 6-digit code that expires | Built from parts: a code stored as a hash with an expiry time, an email, and the sign_in tag | Passwordless Sign-In |
| An answer that never reveals whether an address has an account | Built from parts: the page gives the same answer for every address | Passwordless Sign-In |
| Password reset | Yes | Resetting the Password of an Authenticated User |
| Sign out | Yes | Logging Out an Authenticated User |
| Extra fields on every user, and user profiles | Yes | Creating a User Profile |
| Sign-in with a JWT token | Yes | Authenticating a User with a JWT Token |
| An email allow-list: only listed addresses may sign in | Built from parts: a table of allowed addresses, checked before a link or code is sent | Email Allow-List |
Roles and Permissions
| Capability | Answer | How |
|---|---|---|
| Protect a page or a form with a rule (an authorization policy) | Yes | Adding an Authorization Policy |
| Roles such as admin, stored on the user | Built from parts: a roles field on the user, read by an authorization policy | Admin Role Instead of a Shared Password |
| An admin area for signed-in admins, in place of one shared password | Built from parts: an admin role and a policy on every admin page | Admin Role Instead of a Shared Password |
| Protect a whole page by role | Yes | Associating an Authorization Policy with a Page |
| Show or hide parts of a page by role | Built from parts: a role check inside the page | Admin Role Instead of a Shared Password |
Note: A page with no policy is public. There is no default policy that a page inherits.
Pages and Routing
| Capability | Answer | How |
|---|---|---|
A page at any address you choose, set by its slug | Yes | Pages |
A JSON endpoint at a clean address, such as /api/auth/request-code, with no .json on the end (format: json in the page front matter) | Yes | Logic Engine: API endpoint rules |
| GET, POST, PUT and DELETE endpoints, one method per page | Yes | Pages |
| Layouts and reusable partials | Yes | Reusing Code Across Multiple Pages |
| Redirects | Yes | Redirects |
| Custom error pages | Yes | Custom Error Pages |
A project layout: app/ for your site, modules/<name>/ for code you reuse | Yes | Codebase Introduction |
Data and Imports
| Capability | Answer | How |
|---|---|---|
Your own tables, defined in app/schema/ | Yes | Database Fields and Tables |
| Read and write rows with GraphQL | Yes | Querying Your Databases |
| Search across rows | Yes | Search Introduction |
Import a JSON file of data with the CLI (insites-cli data import) | Yes | Importing JSON or CSV Data |
| Import a CSV file exported from another system | Built from parts: convert it to the import JSON first, then import it | Importing JSON or CSV Data |
| Export data | Yes | Exporting Data |
| Seed or change data when you deploy (migrations) | Yes | Migrating Data |
| Move a whole site from another platform | Yes, for the sources the Insites Migration Tool reads | Migrating to Insites |
| Run work later or in the background | Yes | Background Jobs |
Email and SMS
| Capability | Answer | How |
|---|---|---|
| Email notifications from templates | Yes | Creating an Email Notification |
| Email layouts | Yes | Using Email Layouts |
| Email attachments | Yes | Adding Attachments to an Email Notification |
| SMS notifications | Yes | Creating an SMS Notification |
| Calls to outside services (API call notifications) | Yes | Creating an API Call Notification |
| Safe testing: a staging site sends email only to the test recipients you set | Yes | Staging vs. Production |
| Emails in the person's language | Built from parts: one template per language, chosen by the language the person picked | Multi-Language Sites |
Files
| Capability | Answer | How |
|---|---|---|
| Static files (images, fonts, styles, scripts) served from a CDN | Yes | Using Static Assets on Pages |
| File uploads stored on a row, public or private | Yes | Uploads |
| Generate a PDF | Yes | Generating and Uploading a PDF |
Note: An upload field with no acl setting makes its files public. Set acl: private for files only signed-in people may open.
Languages
| Capability | Answer | How |
|---|---|---|
Translation files, one per language, in app/translations/ | Yes | Translations Introduction |
Show text in the visitor's language with the t filter | Yes | Multi-Language Sites |
Let the visitor choose a language (the language parameter, kept in the session) | Yes | Multi-Language Sites |
| Send the visitor's language to the server and store it, so emails match | Built from parts: a language field on the user or the request row | Multi-Language Sites |
| Dates in each language's format | Yes | Date Format |
User-facing text does not have to be hardcoded in English.
Security
| Capability | Answer | How |
|---|---|---|
| Read the visitor's IP address | Yes: read context.headers.HTTP_X_REAL_IP, which is the same as the first entry of the X-Forwarded-For header. The last entry is an internal address, not the visitor. | Rate Limiting by IP |
| Limit requests per IP address | Built from parts: a table that counts requests per address and time window | Rate Limiting by IP |
| Block an IP address after repeated failures | Built from parts: the same counter, checked before the request is handled | Rate Limiting by IP |
| Lock an account or a form after a number of failed attempts | Built from parts: a failed-attempt counter, cleared on success | Rate Limiting by IP |
Spam protection on forms: reCAPTCHA v2, reCAPTCHA v3 or hCaptcha (the spam_protection tag) | Yes | Form Configuration Options |
Hash, sign and encrypt values (digest, compute_hmac, encrypt, decrypt) | Yes | Filters: Insites |
| Secrets kept out of your code (constants) | Yes | Insites CLI Tool Commands and Options |
Note: Insites has no built-in rate limit or lockout for your own sign-in pages. Build one from the parts above.
Deploying
| Capability | Answer | How |
|---|---|---|
| Separate staging and production sites | Yes | Staging vs. Production |
Deploy from the command line (insites-cli deploy) | Yes | Insites CLI Tool Commands and Options |
| Deploy on every push to GitHub, with history and revert (the Insites GitHub App) | Yes | Insites GitHub App |
| Read your site logs | Yes | Creating Application Logs |
| Custom domains with SSL | Yes, on production sites | Site Domains |
Note: A full insites-cli deploy removes files from the site that are missing from your local build. Add --partial-deploy to keep them.
AI
| Capability | Answer | How |
|---|---|---|
| Build and deploy with any AI assistant that supports remote MCP servers (Insites CloudShell) | Yes | Getting Set Up with AI |
| Let your AI deploy, upload files, read logs and set environment variables | Yes | CloudShell Tools |
| Public rules that teach your AI how Insites works (the Insites Logic Engine) | Yes | Insites Logic Engine |