What you can build
Web apps
A tool people sign in to and work in: a CRM, bookings, invoices, stock. What Setherion builds without being asked, where its data lives, how to share it with a team, and how to ask for one.
A web app is something people work in, not read. A list of clients, the bookings for the week, the invoices that are still unpaid: it opens straight into the screens, keeps what people enter, and each person signs in to their own.
When to choose it
Pick Web App, the grid of tiles above the box on the dashboard, or name the tool in your request: "a CRM", "an app to manage", "a dashboard for".
Web App leaves one thing to your words: whether the app is a tool your team works in, or a product strangers sign up to.
| If you want | Choose |
|---|---|
| A tool for you or your staff: it opens straight into the work | Web App |
| A product people find, sign up to and maybe pay for: a home page first, then accounts, then the app | SaaS |
| Pages for visitors to read | Website |
| Something made for the phone first, with a bar of tabs at the bottom | Mobile App |
What you get without asking
- The working screens first. No marketing page in front: a menu down the side with the four to six sections the tool needs, and the main one already open.
- Sample data from the first second, so you see the tool working before anyone has typed anything into it.
- Add, change and delete for everything in it, with forms, confirmations and messages that say what happened.
- Real accounts. Sign in with Google, or with an email and a password, from the foot of the menu. Signed out, the screens show the sample data. Signed in, each person sees only their own, with an empty state and an Add button until there is something to show.
- Data that stays. What people enter is saved on Setherion's database and is still there after a reload, on any device. Nothing to set up.
- A layout for phones as well as computers.
Ask like this
Name what the tool keeps track of, and what people do with it.
A CRM for a car repair shop: clients and their cars, repair jobs with a status,
parts used, and what each client owesA booking app for a hair salon: the stylists, their services and prices,
a calendar of appointments by day, and a list of clients with their historyAn invoicing app for a freelancer: clients, invoices with items and VAT,
paid and unpaid, and a dashboard of what came in each monthA stock app for a small warehouse: products with quantities and locations,
deliveries in and out, and an alert when something runs lowAlready keep it in a spreadsheet? Press +, then Import an app, then Spreadsheet. The app is built around its columns, and up to 300 of its rows become the app's first data. The rest can go in afterwards, from Manage, then Cloud, then Database. See Import an app.
Pick Web App and leave the box empty, and ideas appear under it. Pressing one puts it in the box, ready to change, and the arrow beside them, Other ideas, shows more.
All the web app ideas
- Online shop
- Client portal
- Invoice board
- Booking system
- Inventory
- Job board
- Course platform
- Support desk
- Recipe library
- Event tickets
Your data
Every web app comes with a database on Setherion, set up for you. You see and manage it in the editor, under Manage, then Cloud:
| Section | What it is for |
|---|---|
| Database | Every record the app has saved. Look through them, change one, add one, import a catalogue. |
| Forms | The messages people sent through the app's forms. |
| Users | The people who have an account in the app, and how they sign in. |
| Emails | The letters the app sends: confirming an account, resetting a password. |
| AI | The app's calls to AI providers, if it has any. |
| Secrets | Keys for other services the app calls, kept on the server, never in the app's code. |
| Logs | Errors visitors ran into, sign-ins, data changes and automatic fixes. |
| Usage | How much the app's database and connections are being used. |
| Advanced settings | Move the app to your own Supabase, pause it, or clear its data. |
Every page is explained in Cloud.
Each plan includes a number of records and a monthly allowance for what published apps do with them. See Pricing. If you would rather keep the data on a database of your own, Advanced settings moves the app to your own Supabase.
Working as a team
By default each account sees only its own records, which is right for an app where every person keeps their own list. For a business where the staff share one list of clients, open Manage, then Cloud, then Users, and mark which accounts are your team. Your team sees and changes every record. You can invite people by email, and they choose their own password.
Make it yours
| To | Ask, or do |
|---|---|
| Add a screen | "Add a Reports page with this month's totals per stylist" |
| Change what is kept | "Each client also has a phone number and a note" |
| Take payments | Connect Stripe, then: "Let clients pay an invoice by card" |
| Send emails | Connect Resend or Brevo, then: "Email the client when a repair is done" |
| Use AI inside the app | Connect OpenAI, Claude or Gemini, then: "Write a summary of each client's history" |
| Let clients reach it from ChatGPT or Claude | Agent integrations |
| Work from a phone | Install it on the home screen, or put it in the stores: Publish to app stores |
Good to know
- Sample data is only shown to people who are not signed in. Once someone signs in, they see what they entered, never the two mixed.
- A tool for your own staff does not need a home page. If people outside your business should be able to find it and sign up, choose SaaS instead.
- An app people can sign up to needs a way to delete their account before Apple accepts it in the App Store. Ask for "a Delete account button beside Sign out".
- With Power Seth a web app gets search, filters, a page for each item, a settings screen and an empty, loading and error state for every list, even unasked. See Build modes.
See it live
SlateBill
An invoicing app: revenue at a glance, invoices with their status, clients. It opens on its sample data.
Was this page helpful?