Services

A new project starts with sign-in and nothing else. Everything else your app might use — storing files, sending email, running work in the background — is a service you turn on when the app needs it.

Sign-in itself isn’t on the Services page: it is part of every project and has its own Sign-in tab of Users & sign-in. That is also where you set the sender name and reply-to address of sign-in mail (verification codes, password resets, invitations).

Turning a service on

The agent asks before it writes code that uses a service that is off. You see a card that says what the app needs it for, whether it costs anything, and how many tables it adds to your database. Choose Turn on, or Not now and the agent builds without it.

You can also open Services and choose Turn on yourself. Either way it is one change to your project. Your Rehearsal and Live servers get the service with the next publish that includes it.

Turning a service off keeps its data. If your code still uses it, Sapilon lists where first.

Email

Your app can send its own mail: receipts, invitations, notices. Mail goes out from your project’s own address.

• On the Build Server, mail is never sent. Open the Email card’s Sent mail to see what the app would have sent, with a preview.
• On Rehearsal, mail goes only to people in your project. Mail to anyone else is held, so a test never reaches a real customer.
• On Live, mail is delivered. An address that bounces or marks mail as spam is not mailed again; Allow again lifts that once its owner has fixed their mailbox.

A daily limit protects your sending reputation, and the card shows today’s count. If many messages bounce, Sapilon pauses your app’s email and support contacts you. Sign-in mail keeps working throughout. There is no separate charge for Email.

Background jobs

Background jobs let your app do work later, on a schedule, or without making people wait: a reminder at 09:00, a report every Monday, a large import.

The Background jobs card lists your app’s jobs (“Every Monday at 09:00, Amsterdam time”), when each runs next, and how its last run went. Run now, Pause and Resume work without a publish. A job that keeps failing shows up in Monitor; Retry runs it again once the cause is fixed. The Build Server runs jobs only while it is awake. There is no separate charge.

Live updates

With Live updates, pages change the moment the data does: a new chat message, a card moved on a board, an order that changed status. Who sees which changes follows your app’s own access rules. Connections recover by themselves after a network drop. There is nothing to configure and no separate charge.

AI search

AI search finds what people mean, not only what they typed: “customers unhappy about delivery” finds the ticket that says “the parcel came three weeks late”, and exact names and numbers still match. Nobody sees a result they couldn’t open.

AI search uses AI and Background jobs, so it turns those on too, and AI asks for a monthly budget first. Indexing and searching draw on that budget. The card shows what is indexed on each server, Rebuild reads everything again, and Try a search lets you check results. When the budget is used up, search keeps working on exact words only.