Start here
Claritty builds software that does work on its own. You describe what you want, or you do the task once while it watches, and it builds the thing, connects it to your tools, and runs it. There are three shapes it can take, and picking the right one is most of the battle.
Three shapes
| What it is | Pick it when | |
|---|---|---|
| An app | A dashboard, home-screen widgets and a database, with agents behind them. | People need somewhere to look at something, and to act on it. |
| An automation | A fixed job that runs on a schedule or a trigger, with no interface. | The same task happens over and over and the steps do not change. |
| A team | A hire you talk to. It decides its own steps per request. | The work arrives in different shapes each time. |
If you can write the steps down in order and they will still be right next month, that is an automation, and it will be cheaper and more predictable than a team doing the same thing.
What Claritty handles
- Hosting
- Your app is online, on its own domain, with a database. There is no server to pick and nothing to keep patched.
- The model
- No Anthropic or OpenAI key to set up. Calls go through Claritty’s proxy and draw on your plan’s credit. You can bring your own key if you would rather.
- Credentials
- The sign-in for every connected service, held per user and never handed to your code.
- Running it
- Schedules, webhooks and retries, plus a record of every run and what it cost.
Two ways to work
Most people never open the code. They describe what they need, answer a few questions, and review what gets built. If you do want the code, every generated project is a normal React frontend and Python backend that you can open, edit and deploy.
Arrived here from GitHub?
This track is about the hosted platform. Claritty Studio, the free desktop app that runs automations on your own machine with your own keys, is the second group in the sidebar. Nothing in it needs an account.