You wanted a workspace: databases, pages, a place to run a team or a life. Thogits is that — records first.
Pages are real screens built on those records. A personal assistant sits on top and writes into the same system of record — in chat, over email, or on a phone call.
This piece is what the product actually is.
Three layers
Thogits is three things that share one set of records: data, pages, and an assistant. The rest of the product is how those three stay honest with each other.
Data
The database is the product, not an accessory.
You store tickets, people, invoices, todos, projects, notes, files — whatever you actually track. Fields are yours. Related records link. You are not stuck in a fixed CRM schema, and you are not stuffing a spreadsheet into a doc so you can filter it.
Open Data when you want the raw list. Open a page when you want a designed screen. Ask the assistant when you want the record written without opening either. Same records, three ways in.
A record can be more than one thing at once. A person can be a customer and a vendor. A piece of work can be a ticket and a personal todo. You do not duplicate the entity just to satisfy a table.
Read more on data.
Pages
Pages are not blocks you click together. They are screens built on your records: lists, boards, forms, detail views, dashboards.
You describe the screen. You get something you can use on the web and on iOS. Not a mockup. Not a prototype you export.
When the process changes, you change the page. Add a field. Rename a status. Ask for a different layout. The records stay. The screen moves.
That is why this is not a pile of docs with a table in the middle. The table is the system. The page is a working surface on top of it.
You can start from a blank description, or merge in an installable starting system and reshape it. Either way, the page is software on your data.
See how pages work and the full feature list.
Assistant
The assistant is a personal operator on your space. Chat in the product. Email. Phone calls.
It does not only summarise. It writes records. “Add this invoice.” “Move that ticket.” “What’s overdue?” The answer and the mutation land in the same database the pages show.
Scheduled automations wake it later: a weekly chase, a reminder, a repeating check. Automations here are scheduled work, not a maze of recipes you wire by hand.
Other agents can see and edit records through MCP. MCP is a records door. It does not build pages. If you bring Claude or another client, it can work on the data. The generated screens stay in Thogits.
More on agents.
A business or a life
You can run a small business on this. You can run a personal system on this. Same three layers.
The space is the unit. You invite people into it. A team sharing one system of record — not a permission matrix for hiding pages from each other.
Web and iOS stay in sync. That is the product. We do not sell an offline mode.
Templates are installable starting systems — a CRM, a ticket tracker, a project board you merge in and then change. They are a way to start, not a finished product you are stuck with.
What people actually put in it
The shape is yours. These are the jobs that show up first.
- Tickets. Intake, status, owner, notes. A board for the team. An assistant that files what arrives by email.
- CRM. People, companies, next step, last contact. A pipeline page. A call that logs the follow-up as a record.
- Directory. Staff, vendors, rooms, equipment. Searchable records, not a stale spreadsheet sitting inside a doc.
- Todos. Personal or shared. Linked to a project or a person when that is the truth.
- Docs. Notes that live next to the record they belong to, not in a parallel wiki you have to keep honest.
- Projects. Milestones, tasks, files, the people on the job. Pages for the plan; data for the facts.
- Invoices. Amounts, status, who owes what. A list you can filter. An assistant that can draft the next one as a record.
If you want a shared space, start at for teams. If this is for you, not a company, for personal use. Tickets, CRM, docs, and the rest live under use cases.
How it feels day to day
Morning: open a page, scan the board, update three records.
Afternoon: the assistant emails you what is still open. You reply. It writes the status change.
Later: you are not at a desk. You call. You tell it the job finished and the invoice should go out. The records update. The next time someone opens the page, that is what they see.
You did not copy anything into a spreadsheet. You did not ask a chatbot for advice and then type it in yourself. The assistant and the pages share the database. If it is not in the record, it did not happen.
The same loop works for a life: todos, notes, people you need to remember, a project that is just “move house.” You do not need a company to justify a system of record.
What this is not
It is not a writing surface with a table glued on. Docs here live on the same records as the work.
It is not a permission system for a large organisation. Invite the people doing the work.
It is not an MCP page factory. Other agents can read and edit records. They do not build the pages.
It is not offline-first. Use it on the web and on iOS; they sync.
Try it
Describe a system you already run in a spreadsheet, another workspace, or your head. Get records, a page, and an assistant on the same space.
Sign up. An account is free, and a new organisation starts a 30-day trial. See pricing. Read features, then the layers: data, pages, agents. How it stacks up against other tools: Compare. More writing lives on the blog.