Open source · Free while in beta
The last SaaS you'll ever need.
Records, files, reminders, and permissions, kept in one system any AI assistant can operate. Describe what you need, and your assistant sets it up, runs it, and changes it as your work changes.
You don't open an app to see your data. You ask, and the answer comes back already shaped. The interface is simply your Claude, your ChatGPT, or whichever assistant you already use.
Join the beta or host it yourself
Here's what setup looks like. Expand a row for the details.
Setting that up now.
Created collection · Applicants
- Fields
- Name · Role · Stage · Résumé · Salary notes
- Role
- Designer / Support Lead
- Stage
- Applied → Screen → Interview → Offer
Added rule · Sarah ↔ Applicants
- Can
- view and edit every applicant
- Except
- the Salary notes field
Invited sarah@sundialstudio.com
- As
- member
- Status
- invitation sent
Scheduled digest · Mondays 9:00
- Sends
- new applicants, by role and stage
- To
- you, by email
Done. Applicant tracking is live. Sarah has an invitation waiting; she'll see every candidate and never the salary notes. Your first digest arrives Monday at 9. Forward me a résumé whenever you're ready, or just tell me who applied.
Added. It's on every applicant now, blank until you fill it.
Updated collection · Applicants
- Added
- Referred by
- "Track invoices and nudge me before they're due."
- "Keep the club's waivers and who has signed."
- "Plan the launch: tasks, owners, a Friday status ping."
That's the whole product. The Last SaaS is a server that holds your work, and it has no screens of its own. Your assistant connects to it via MCP, and the conversation is the interface.
01You've set this app up before.
Hiring gets a tracker, clients get a base, the launch gets a board, and the bill grows a line each time. Underneath, they are the same product. What changes is the branding and the per-seat price.
- Renews monthly
Applicant tracker$29/seatClient base$25/seatProject board$12/seatForm builder$59/mo- One system your assistant operates $0 in beta
The parts are already here. Your assistant turns them into an applicant tracker, a client base, or whatever you need next.
Setup is a conversation, and so is every change after it. Configuring software is precise, repetitive work: exactly what your assistant is good at, and exactly what you're tired of.
02Your assistant is the frontend now.
Every SaaS you subscribe to is a database with a translation layer on top: forms going in, dashboards coming out. That layer is most of what you were paying for, and it is exactly the work a model does well. Ask how the quarter is going, and the answer is drawn in the window you asked from. Nobody built that dashboard, and nobody has to keep it current.
Read collection · Invoices
- Query
- issued Jun 1 – Aug 31
- Fields
- Amount · Status · Client
- Matched
- 12 records
You've collected $18,400 of the $23,900 invoiced. Two invoices are overdue, both from Meridian.
Shown in Claude Desktop. Any assistant connected over MCP reads the same records and can draw the same chart.
The interface isn't gone. It's whatever you just asked for.
03The pieces every tool is made of.
Six primitives cover what trackers, bases, and boards are made of. They are built once and shared by every problem you point them at:
- Records. Structured lists of anything: applicants, invoices, inventory. Your assistant shapes the fields to your work and keeps every entry valid.
- Files. Résumés, contracts, photos, attached to the records they belong to instead of scattered across a drive.
- People. Invite a teammate in a sentence. Everyone works from the same source of truth, with their own assistant or none at all.
- Permissions. Rules down to the row and the field. The intern sees the schedule, not the salaries.
- Reminders. Digests, due-date nudges, weekly pings. Recurring or one-off, scheduled in a sentence.
- History. Every change is recorded with who made it and when, whether it was a person or an assistant.
04Everyone gets their own view.
Permissions apply to people and to their assistants. Your bookkeeper's assistant can read every invoice and can't open payroll. The boundaries your team already works by live in one place instead of five.
- Rule · Marta, bookkeeping
- can view and add records in Invoices
- can attach files to any invoice
- not the Payroll collection
- not the Margin field on invoices
Rules are plain sentences, said once. They apply to a person, to their assistant, and to anyone they invite, down to a single field on a single record. History records every change and who made it, so "who changed this?" is one question to your assistant.
05Open source and portable.
The Last SaaS is open source, and the hosted version is free during the beta. Your data exports with one command, and the server is yours to run yourself, now or if you ever decide to leave.
06Get started in three steps.
- Create an account
- Connect your assistant
- Say what you need
Works with any assistant that speaks MCP: Claude, ChatGPT, Cursor, or your own agent. Prefer a terminal? There's a CLI.
Hi, I'm Mike. I got tired of setting up the same app over and over, so I'm building the last one.