How the suite fits together
Which app owns which job, and which records are shared so you only create them once.
Each app does one job. ShellStack assembles the organisation and then hands you to the app that holds the work. The same person, the same client and the same project are reused, so a task, an hour and a page can point at one another.
| You want to… | Open |
|---|---|
| Invite people, set access, manage the plan | ShellStack |
| See today across the suite | Today, in any app |
| Record hours, approve a week, invoice | TurtleTime |
| Plan who is on what this week | TurtleTime → Forecast |
| Run client work on a board | Tides |
| Write the spec, notes or a diagram | Kraken |
| Capture a short dated note | Kraken → Memo, or ShellStack → Calendar → My Notes |
| Ask an AI teammate to do governed work | Shelly |
| Connect an outside app and map it to a client | Bridge, in the app that should receive the data |
| Read suite-wide numbers | ShellStack → Dashboard |
Shared records
- People are one account. Product access is a tick on that membership, not a separate login.
- Clients and projects are created once. TurtleTime uses them for time and invoices. Tides uses them for boards. Kraken can hang a page on the same client or project.
- Time is one ledger. An hour started in TurtleTime and an hour logged on a Tides task are the same kind of record, with a source so you can see where it was written.
- A workspace is the boundary. Switch workspace and you switch the clients, hours, tasks and pages you are looking at.
What ShellStack does not do
ShellStack does not contain the board, the timer, the wiki or the crew. It launches them. Organisation workspaces are renamed, staffed and billed here. Inside a product, those organisation controls are read-only and link back.