Starter backends
Apso includes 27 starter briefs in the service builder. A starter gives the schema builder a detailed product model with entities, fields, statuses, and relationships. You can edit the brief before Apso creates the .apsorc schema.
Each starter focuses on the backend data model. Add your own business rules in extensions/ and connect a frontend after the generated API matches your product.
Use a starter effectively
- Open the Apso service builder and create a service.
- Choose the starter closest to your product. Use its structure as a baseline.
- Edit the brief before generation. Remove entities you do not need and name the concepts the way your team does.
- Review the proposed entities, fields, and relationships in the schema editor.
- Generate the backend and inspect the API documentation before adding custom behavior.
- Put webhooks, calculations, approvals, and other product rules in
src/extensions/. - Connect the backend to Next.js, React, React Native, or Flutter.
SaaS essentials
These starters cover backend capabilities that appear across many subscription and team products.
| Starter | Core model |
|---|---|
| User Auth & Teams | Users, organizations, memberships, invitations, roles, sessions, password resets, and audit events |
| Subscription Billing | Plans, plan features, customers, subscriptions, invoices, payments, usage records, and coupons |
| Multi-Tenant Workspaces | Workspaces, scoped members, invitations, settings, domains, billing, API keys, webhooks, and limits |
| Notification System | Templates, preferences, notifications, delivery logs, push tokens, digests, and channels |
| Webhook Management | Webhooks, signed deliveries, event types, retries, integrations, mappings, and OAuth connections |
| Audit Logs & Compliance | Audit events, retention policies, export and deletion requests, consent, allowlists, and access reviews |
| File Upload & Media | Files, folders, versions, shares, transforms, upload sessions, storage buckets, and thumbnails |
| Feature Flags & A/B Testing | Flags, targeting rules, segments, experiments, results, overrides, schedules, and SDK keys |
| Waitlist & Early Access | Waitlists, entries, referrals, rewards, invitation batches, updates, and access codes |
Customer platforms
| Starter | Core model |
|---|---|
| Customer CRM | Contacts, companies, deals, pipeline stages, activities, notes, tasks, email records, tags, and reports |
| Support Ticketing | Tickets, replies, agents, teams, tags, canned responses, SLA policies, satisfaction, macros, and views |
Application patterns
Use these starters when the product itself follows a familiar web application model.
| Starter | Core model |
|---|---|
| Project Management | Projects, milestones, tasks, dependencies, teams, comments, time entries, sprints, and boards |
| Issue Tracking | Issues, projects, users, comments, labels, history, attachments, sprints, and time tracking |
| Knowledge Base | Articles, categories, revisions, authors, feedback, search records, and access settings |
| E-Commerce Store | Products, variants, categories, carts, orders, order items, payments, inventory, and promotions |
| Learning Platform | Courses, modules, lessons, instructors, enrollments, progress, quizzes, submissions, and certificates |
| Survey & Feedback | Surveys, question types, responses, answers, branching rules, collectors, and analysis records |
| Job Board & ATS | Jobs, candidates, applications, interviews, scorecards, hiring stages, offers, and referrals |
| Event Management | Events, sessions, speakers, attendees, tickets, sponsors, venues, check-ins, and feedback |
| Blog & CMS | Posts, authors, categories, tags, comments, media, pages, revisions, SEO metadata, and newsletters |
Industry systems
These starters provide domain vocabulary and entity coverage for operational products.
| Starter | Core model |
|---|---|
| Inventory Management | Products, warehouses, stock levels, purchase orders, suppliers, movements, transfers, and counts |
| Property Management | Properties, units, tenants, leases, maintenance requests, payments, and vendors |
| Point of Sale | Menu items, modifiers, tables, orders, order items, payments, staff, and reservations |
| Patient Records | Patients, providers, appointments, clinical records, prescriptions, billing, and insurance |
| Hotel Booking | Properties, room types, rooms, rates, reservations, guests, payments, and housekeeping |
| Gym Membership | Members, plans, subscriptions, classes, trainers, bookings, attendance, and payments |
| Fleet Management | Vehicles, drivers, trips, routes, maintenance, fuel logs, inspections, and incidents |
From starter to full-stack application
A productive first implementation usually follows this order:
- Generate only the entities needed for the first user workflow.
- Run the API locally and verify create, list, update, and delete behavior.
- Add authentication and tenant scope before connecting protected frontend routes.
- Create a server-side Apso SDK client for a Next.js BFF or call the REST API from another frontend.
- Add one product workflow at a time in
extensions/, with tests around each rule. - Use
apso migratewhen the schema changes and commit the resulting migration files.
Last updated on