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. When you need a new field or a different rule, you say so.

Instead of opening an app to see your data, you ask, and the answer comes back already shaped. The interface is 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.

• "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 records and files, and it has no user interface of its own. Your assistant connects to it via MCP, and the conversation is the interface.

01Most SaaS is the same parts underneath.

If you run a small team, the bill usually reads like this: one subscription per problem, each one set up by hand.

• Renews monthly
• Applicant tracker $29/seat
• Client base $25/seat
• Project board $12/seat
• Form builder $59/mo
• One system your assistant operates $0 in beta

Underneath, an asset tracker is a list of gear and a rule about who sees the price column. A client base is the same list with different fields. The Last SaaS keeps the parts, and your assistant assembles whichever app you ask for.

Setup is a conversation, and so is every change after it. Configuring software is precise, repetitive work, and models do it reliably. Every action is recorded in the audit log, so you can see exactly what changed.

02Your assistant is the frontend now.

Every SaaS you subscribe to is a database with a user interface on top: forms going in, dashboards coming out. That interface is most of what you were paying for, and it is work a model now does well. Ask how the quarter is going, and your assistant reads the records and draws the chart in the window you asked from. The dashboard doesn't exist until you ask, so it is never out of date.

Shown in Claude Desktop. Any assistant connected over MCP reads the same records and can draw the same chart.

Join the beta and ask the same question with your own data

03The pieces every tool is made of.

Six primitives cover what these apps are made of. Each is built once and shared by everything you use the system for:

• Records. Structured lists of anything from gear to invoices. Your assistant shapes the fields to what you're tracking and keeps every entry valid.
• Files. Receipts and contracts, 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. Due-date nudges and weekly digests, 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.

This is also the difference between The Last SaaS and a spreadsheet or a Notion base with AI attached. Those are apps built for clicking, with an assistant invited in afterward. This is a server built for agents to operate from the start, and the permissions and history above are what make that safe.

04Everyone gets their own view.

Permissions apply to people and to their assistants. Your bookkeeper's assistant can read every invoice and cannot open payroll. The rule is stated once and enforced on every request.

• Rule · The bookkeeper
• can view and add records in Invoices
• can attach files to any invoice
• not the Payroll collection
• not the Margin field on invoices

A rule reaches down to a single field on a single record, and it covers any assistant acting for that person. History records every change and who made it, so "who changed this?" has an answer.

05Open source and portable.

The Last SaaS is open source, and the hosted version is free during the beta. When paid plans arrive, beta accounts keep a founding rate. Self-hosting stays free either way: 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.

1. Create an account
2. Connect your assistant
3. Say what you need

Join the beta Free while in beta. No card, no sales call.

Connecting is one paste. In Claude, it's Settings → Connectors → Add custom connector: paste your workspace's MCP address and approve the sign-in. Cursor and other MCP clients take the same address. The ChatGPT desktop app takes a custom connector the same way; on the web it currently requires a business workspace, and an app directory listing is planned. 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.