Features

Everything Squid does. One brain behind all of it.

38 features in 6 groups: the backlog, the code, the rules, the day, the people and the numbers, sharing one record, so nothing is ever copied from one place to another.

Plan and build7 features · From idea to the sprint Code and Kraken5 features · The code, and an assistant Get it right6 features · Rules, gates and the record Run the day7 features · Presence, time and leave Grow together7 features · Feed, growth and check-ins See where you stand6 features · Reports and operations

Plan and build Code and Kraken Get it right Run the day Grow together See where you stand Meet Kraken

01From idea to the sprint

Plan and build

One backlog from the big idea down to the smallest step, sprints planned to what people can carry, and a board that moves as the work does.

Backlog

Every piece of work sits in one tree: initiative, epic, feature, story, task and step. Filter by wave, module or readiness, open any record in place, and see at a glance what is Ready and what holds the rest.

Six levels, one place — no second tool for the detail
Stories written as As a / I want / So that, with Given / When / Then criteria
Search, filter and open any record without leaving the list

Product backlog

Initiative · Epic · Feature · Story

Product backlog

2 initiatives

Work shaped by readiness, architecture and delivery rules.

BacklogRefinementBacklog hygiene

Work itemTypeScopeState

Set up and find an organisationEP-01Epic8 storiesReady

Create a workspaceST-31Story5 criteriaReady

Invite people by emailST-42Story3 criteriaReady

Find a workspace by nameST-38Story4 criteriaRefine

Sign in and manage your accountEP-02Epic6 storiesPlan

Plan and roadmap

The roadmap, the releases and the sprints, planned from Ready stories in dependency order and filled to what each person can carry. A committed sprint stays committed; the rest is a forecast that updates itself.

Sprints fill to each person’s capacity
Dependencies order the plan for you
Re-plans are proposed, explained and accepted, never silent

Sprint board

Each person has a lane, each story a stage. Tick the steps and the story moves along — from in progress to review, test and done — so the board always tells the truth without anyone dragging cards.

Stories move as their steps are ticked
Blocked work stands out at once
The sprint’s leaders, quietly, beside the header

Tasks, steps and timer

Each task breaks into the steps that finish it, and a timer runs on the task you are on. Time lands on the work it belongs to, and the timesheet writes itself.

A timer on every task, one at a time
Steps that count towards the story’s stage
Time added by hand when you forgot

Projects

Every project in one place, each a whole record of its own: what is being built now, what is up next, and what waits its turn. Only a project’s members open it; everyone else sees its name and a lock.

A list, or three columns by stage
Members only, with teams
Open one and Squid switches to it

QA and test cases

Every acceptance criterion becomes a test case at the levels it needs. A pass is only a pass with a green CI run behind it, checked against the real run — and the QA lead signs.

Test cases drawn from the criteria
Results pulled from CI and checked
A test plan you can copy or export

Export

Take anything out: a story as Markdown, the sprint as CSV, the whole working state as a file. Squid never holds your work hostage.

Stories, sprints and test plans as text
The working state as one file
Copy-ready for chat and docs

02The code, and an assistant

Code and Kraken

Repositories, branches and pull requests next to the stories they deliver, and Kraken, an assistant that knows your work and the way your team runs it.

Source code

Squid keeps the code with the work: repositories with a file explorer, commits and line diffs, editing in the browser, and a small squid command to commit and push from your computer. There is no Git server to run.

Every repository starts with main, stage and dev
Commits, diffs and history for every branch
A squid command for your own machine

Branches and pull requests

Nobody pushes straight to main, stage or dev. Work happens on branches named for what they carry, feat/ or fix/, and moves one step at a time through pull requests: into dev, then stage, then main.

Starting a task opens its branch, from the base you pick
Reviews tied to the version reviewed
Conflicts resolved together, file by file

Private repositories

A repository is open to its project’s team, or private to its owner and the people given access. Each person is a writer or a guest who only reads.

Hidden from everyone else
Write or guest, person by person
The owner and admins decide

Environment and secrets

Variables for development, staging and production, kept with the repository. Secrets are sealed and shown as dots; revealing or copying one is logged, never its value.

Import a pasted .env
Pull an environment to a local file
Who did what, without the values

Kraken, the assistant

Kraken answers from the page you are on. It checks whether a story is right and says what holds it back, tells you the next step, explains any part of Squid, and rewrites a line when you ask. It suggests; you decide and you save.

Knows the record you have open
Runs on free models, or your own key
Never changes anything by itself

03Rules, gates and the record

Get it right

Your delivery manual turned into rules Squid checks on every record, gates that decide with evidence, and an architecture that stays next to the work.

Rules and the Ready gate

Every rule from your delivery manual is checked on every story — a So that, a failure case per criterion, requirements covered, the architecture impact assessed. Ready is the result of the rules, and the gate says exactly what holds a story back.

Over a hundred rules, checked on every story
Each failing rule says how to fix it
A rules board for the whole backlog

Process map

Delivery manual

Process map

9 stages

Every step, decision and evidence trail in one place.

MapStepsGapsRules

01 · 2 gatesBaselineArchitecture agreed

02 · 1 gateDiscoverProblem defined

03 · 3 rulesRefineStories sliced

04 · 1 gateBuildWork in motion

05 · 1 gateVerifyEvidence linked

06 · 1 gateReleaseGo / no-go

Gates

Discover, Ready, Verify, Release and the architecture Baseline each have a gate, decided by the person who holds that role, with the evidence on the table. Nobody approves their own work.

Process roles: Product, Architecture, QA leads
Every decision kept with its evidence
Queues of what waits for you

Architecture record

Modules and who owns which data, standards, decisions (ADRs), system designs and cross-cutting lenses — kept in Squid, drawn as a map, and checked against each story. Change a decision and the stories that rest on it are marked for a re-check.

ADRs and designs next to the stories they shape
An impact check on every story
Stale work flagged when a decision changes

Process guide

Every step from idea to production: who acts, which rules check it, what evidence it leaves. A guided journey for newcomers, and the map for everyone else.

Nine stages, six gates, one map
A guide for the stage each story is in
Plain language, no jargon

Review queue

Squid’s agent does process work through change sets: drafts, refinements, decisions. Each edit waits in a queue for a person to accept or reject, with its reason, and every change keeps its history.

Edit by edit, accept or reject
Who changed what, and why, forever
Conflicts caught before they overwrite

Backlog health

See the backlog as a whole: what blocks Ready most often, how the waves fill, which stories need a design, and where the delivery model is not yet followed.

The most common blockers, counted
Waves and modules at a glance
Gaps in the model, named

04Presence, time and leave

Run the day

Check in, see who is around, give your standup, keep your shift — with late time made up, overtime counted and leave on the calendar.

Attendance, shifts and overtime

Check in and out from the header. Pick your shift; Squid shows how much of it is covered, when a late start has been made up, and the overtime past the shift — live in the Today box, by the month on your profile, and for the whole team for the admin.

Late is made up by working the shift’s length
Overtime counted past a mark the admin sets
Timesheets and a day log, built from the clock

Member profile

Team · Profile

Maya Chen

Tech LeadIdentity & accessBuilding with the team since Sprint 1

12Stories shipped

6Reviews

4Badges

Today box and guide

A small box that opens when the day starts: the task you are on, the next one, your shift, and the guide for the stage your story is in — so nobody has to ask what comes next.

Now and next, from your sprint lane
The guide for each stage of the work
Folds away to a single line

Standups

Squid drafts yesterday and today from what you ticked and timed. Add the blockers, send it, and the team sees every standup in one place.

A draft from your own work
Blockers that reach the right people
Everyone’s standup on the team page

Leave

Apply for annual, sick, casual or unpaid leave — or half a day. Squid counts the working days on your shift, shows what is left of the year, and the admin approves with a note. Approved leave is on everyone’s calendar and out of the shift.

Counted in working days, holidays left out
Approve or reject, with a reason
The kind and reason stay private

Calendar

Meetings and who is invited, events and holidays for everyone, private reminders, leave — beside the sprints, their planning and review days, and your own lane.

Month, week, day and agenda
Join a meeting straight from its entry
The sprint cadence drawn for you

Meetings

Audio and video calls without another app: start one now with an agenda and the people you need, or join from the calendar. Minimise it to a small floating window and keep working while you talk.

Chat and participants beside the call
A floating window that follows you around Squid
Calls kept to time, with a countdown

Team and presence

Working, in a meeting, back in five, at lunch: the team’s status at the foot of every page, and the sprint’s work per person on the team page.

A status anyone can set in a click
Each person’s sprint at a glance
Never times — those are the admin’s

05Feed, growth and check-ins

Grow together

A feed of what the team did, a place to ask, a ladder to climb with skills scored from real code reviews, and short check-ins that tell you how people are.

Feed

Everything worth knowing, as it happens: announcements to answer, wins, work finished, gate decisions, shout-outs and what the team said in its check-ins — with comments and reactions.

Built from the work, never posted twice
Announcements people answer
Mentions that reach you

Team feed

Team

What moved today

EverythingWinsWork done

Maya closed the release gateInvite flow passed QA and is ready to ship.

Theo earned a review badgeThoughtful review on the workspace permissions story.

Leo moved a story to ReadyAll criteria and failure cases are now checked.

Questions

Ask the team anything, mention who should answer, run a quick poll, and mark the answer. Unanswered questions surface before they go stale.

Polls and accepted answers
What needs you, counted in the header
Stale questions raised

Growth and code reviews

Every story that reaches review gets a code review of its branch, scored skill by skill. Skills build into a stage and a rung on the ladder, with what to improve next.

Skills scored from the code, not opinion
A ladder with clear next steps
Badges for the moments that matter

Leaderboard

Tasks, steps, standups and days in, scored for the sprint. The podium is kept, so a place earned is a place remembered.

Scored from the work itself
Podiums and firsts kept
Badges for streaks and finishes

Messages from the admin

The admin writes to everyone, a role or chosen people. It lands in the bell and in Messages; an important one opens first at the next sign-in, and the admin sees who has read it.

Groups by role or process role
Important ones open on arrival
Read receipts, and a note when all have read

Team check-ins

Short check-ins a few days apart — the week’s weather, a battery, three words for the team, a shout-out — that tell the admin how people really are, with warnings before they become exits.

A minute or two, a few days apart
Anonymous by default
Trends and warnings for the admin

Notifications

Assigned, mentioned, a badge unlocked, leave decided, a shout-out — a toast the moment it happens and a bell that remembers.

No feed to watch
Each one opens where it points
Seen across every open tab

06Reports and operations

See where you stand

The project at a glance, reports that write themselves, and production feeding back into the backlog.

Reports and pulse

A daily and weekly status, written from the work: what finished, what moved, who is blocked and whether the sprint will land — with a pulse score and the signals behind it, ready to paste into chat.

On track, at risk or off track — with reasons
Copy-ready for Slack or email
Momentum over the last two weeks

Project reports

Reports

The pulse of the project

On track

Momentum, blockers and quality from the work recorded today.

PulseEnd of dayWeekly

84Project health+4 since last week

Sprint pace83%On track

Ready work28+6 this week

Open blockers2Needs attention

Quality92%Evidence linked

Today’s signalDelivery is steady. Two blocked stories need a decision before planning closes.

Dashboard

Initiatives, readiness, flow and the sprint in one view, kept current as the work changes.

Readiness by initiative
Flow through the stages
Always current

Operate

Defects with their severity, incidents, readings and feedback from production — triaged, and turned into new stories when they are work.

Severity from your own list
Production readings against goals
Feedback becomes backlog

Goals

Squid sets the goals from the project itself: what the year and the quarter must release, each initiative’s part, the sprint for the organisation, each team and each person’s lane, and the pace for the day. Each counts itself from the work and shows where it stands against the time gone; people add their own and align them.

Daily, weekly, sprint, monthly, quarterly, yearly
Organisation, teams and people, aligned
Counted from tasks, stories and releases

Feedback portal

Anyone can report a bug, a gap or an idea against the part of Squid it touches, from any page. The admin triages it, and the reporter hears back.

Against the feature it is about
Triage with a note back
Nothing lost in chat

System status

Whether the database answers, when the last change and the last CI result landed, and what waits for review.

Database health
The agent’s last call
CI and review at a glance

Live in Squid

Meet Kraken, the assistant in Squid

An assistant that knows Squid and your work. Ask it anything: it explains, checks, says what comes next, and rewrites a line when you ask. It never changes anything by itself. You decide and you save.

1Is this right?It runs the rules and the gates on a story, a feature or a decision, and says plainly what holds it back and how to fix it.
2What do I do next?From the page you are on and what is waiting on you: one next step, then the few after it.
3Explain itAny gate, rule, lens or feature in Squid, in plain words, with where it comes from.
4Rewrite itA story, a criterion or a requirement, reworded to read well and pass the rules, as a suggestion you can use.

Kraken suggests. Your team decides. What comes after it

See it on your work.

Squid is opening to a few teams at a time. Leave your email and tell us what you use today.

Back to the tour

by Coderatory

Initiative → Epic → Feature

Features

Everything Squid does. One brain behind all of it.

38 features in 6 groups: the backlog, the code, the rules, the day, the people and the numbers, sharing one record, so nothing is ever copied from one place to another.

Plan and build Code and Kraken Get it right Run the day Grow together See where you stand Meet Kraken

01From idea to the sprint

Plan and build

One backlog from the big idea down to the smallest step, sprints planned to what people can carry, and a board that moves as the work does.

Backlog

Six levels, one place — no second tool for the detail
Stories written as As a / I want / So that, with Given / When / Then criteria
Search, filter and open any record without leaving the list

Product backlog

Initiative · Epic · Feature · Story

Product backlog

2 initiatives

Work shaped by readiness, architecture and delivery rules.

BacklogRefinementBacklog hygiene

Work itemTypeScopeState

Set up and find an organisationEP-01Epic8 storiesReady

Create a workspaceST-31Story5 criteriaReady

Invite people by emailST-42Story3 criteriaReady

Find a workspace by nameST-38Story4 criteriaRefine

Sign in and manage your accountEP-02Epic6 storiesPlan

Plan and roadmap

Sprints fill to each person’s capacity
Dependencies order the plan for you
Re-plans are proposed, explained and accepted, never silent

Sprint board

Stories move as their steps are ticked
Blocked work stands out at once
The sprint’s leaders, quietly, beside the header

Tasks, steps and timer

Each task breaks into the steps that finish it, and a timer runs on the task you are on. Time lands on the work it belongs to, and the timesheet writes itself.

A timer on every task, one at a time
Steps that count towards the story’s stage
Time added by hand when you forgot

Projects

A list, or three columns by stage
Members only, with teams
Open one and Squid switches to it

QA and test cases

Every acceptance criterion becomes a test case at the levels it needs. A pass is only a pass with a green CI run behind it, checked against the real run — and the QA lead signs.

Test cases drawn from the criteria
Results pulled from CI and checked
A test plan you can copy or export

Export

Take anything out: a story as Markdown, the sprint as CSV, the whole working state as a file. Squid never holds your work hostage.

Stories, sprints and test plans as text
The working state as one file
Copy-ready for chat and docs

02The code, and an assistant

Code and Kraken

Repositories, branches and pull requests next to the stories they deliver, and Kraken, an assistant that knows your work and the way your team runs it.

Source code

Every repository starts with main, stage and dev
Commits, diffs and history for every branch
A squid command for your own machine

Branches and pull requests

Nobody pushes straight to main, stage or dev. Work happens on branches named for what they carry, feat/ or fix/, and moves one step at a time through pull requests: into dev, then stage, then main.

Starting a task opens its branch, from the base you pick
Reviews tied to the version reviewed
Conflicts resolved together, file by file

Private repositories

A repository is open to its project’s team, or private to its owner and the people given access. Each person is a writer or a guest who only reads.

Hidden from everyone else
Write or guest, person by person
The owner and admins decide

Environment and secrets

Variables for development, staging and production, kept with the repository. Secrets are sealed and shown as dots; revealing or copying one is logged, never its value.

Import a pasted .env
Pull an environment to a local file
Who did what, without the values

Kraken, the assistant

Knows the record you have open
Runs on free models, or your own key
Never changes anything by itself

03Rules, gates and the record

Get it right

Your delivery manual turned into rules Squid checks on every record, gates that decide with evidence, and an architecture that stays next to the work.

Rules and the Ready gate

Over a hundred rules, checked on every story
Each failing rule says how to fix it
A rules board for the whole backlog

Process map

Delivery manual

Process map

9 stages

Every step, decision and evidence trail in one place.

MapStepsGapsRules

01 · 2 gatesBaselineArchitecture agreed

02 · 1 gateDiscoverProblem defined

03 · 3 rulesRefineStories sliced

04 · 1 gateBuildWork in motion

05 · 1 gateVerifyEvidence linked

06 · 1 gateReleaseGo / no-go

Gates

Discover, Ready, Verify, Release and the architecture Baseline each have a gate, decided by the person who holds that role, with the evidence on the table. Nobody approves their own work.

Process roles: Product, Architecture, QA leads
Every decision kept with its evidence
Queues of what waits for you

Architecture record

ADRs and designs next to the stories they shape
An impact check on every story
Stale work flagged when a decision changes

Process guide

Every step from idea to production: who acts, which rules check it, what evidence it leaves. A guided journey for newcomers, and the map for everyone else.

Nine stages, six gates, one map
A guide for the stage each story is in
Plain language, no jargon

Review queue

Edit by edit, accept or reject
Who changed what, and why, forever
Conflicts caught before they overwrite

Backlog health

See the backlog as a whole: what blocks Ready most often, how the waves fill, which stories need a design, and where the delivery model is not yet followed.

The most common blockers, counted
Waves and modules at a glance
Gaps in the model, named

04Presence, time and leave

Run the day

Check in, see who is around, give your standup, keep your shift — with late time made up, overtime counted and leave on the calendar.

Attendance, shifts and overtime

Late is made up by working the shift’s length
Overtime counted past a mark the admin sets
Timesheets and a day log, built from the clock

Member profile

Team · Profile

Maya Chen

Tech LeadIdentity & accessBuilding with the team since Sprint 1

12Stories shipped

6Reviews

4Badges

Today box and guide

A small box that opens when the day starts: the task you are on, the next one, your shift, and the guide for the stage your story is in — so nobody has to ask what comes next.

Now and next, from your sprint lane
The guide for each stage of the work
Folds away to a single line

Standups

Squid drafts yesterday and today from what you ticked and timed. Add the blockers, send it, and the team sees every standup in one place.

A draft from your own work
Blockers that reach the right people
Everyone’s standup on the team page

Leave

Counted in working days, holidays left out
Approve or reject, with a reason
The kind and reason stay private

Calendar

Meetings and who is invited, events and holidays for everyone, private reminders, leave — beside the sprints, their planning and review days, and your own lane.

Month, week, day and agenda
Join a meeting straight from its entry
The sprint cadence drawn for you

Meetings

Audio and video calls without another app: start one now with an agenda and the people you need, or join from the calendar. Minimise it to a small floating window and keep working while you talk.

Chat and participants beside the call
A floating window that follows you around Squid
Calls kept to time, with a countdown

Team and presence

Working, in a meeting, back in five, at lunch: the team’s status at the foot of every page, and the sprint’s work per person on the team page.

A status anyone can set in a click
Each person’s sprint at a glance
Never times — those are the admin’s

05Feed, growth and check-ins

Grow together

A feed of what the team did, a place to ask, a ladder to climb with skills scored from real code reviews, and short check-ins that tell you how people are.

Feed

Everything worth knowing, as it happens: announcements to answer, wins, work finished, gate decisions, shout-outs and what the team said in its check-ins — with comments and reactions.

Built from the work, never posted twice
Announcements people answer
Mentions that reach you

Team feed

Team

What moved today

EverythingWinsWork done

Maya closed the release gateInvite flow passed QA and is ready to ship.

Theo earned a review badgeThoughtful review on the workspace permissions story.

Leo moved a story to ReadyAll criteria and failure cases are now checked.

Questions

Ask the team anything, mention who should answer, run a quick poll, and mark the answer. Unanswered questions surface before they go stale.

Polls and accepted answers
What needs you, counted in the header
Stale questions raised

Growth and code reviews

Every story that reaches review gets a code review of its branch, scored skill by skill. Skills build into a stage and a rung on the ladder, with what to improve next.

Skills scored from the code, not opinion
A ladder with clear next steps
Badges for the moments that matter

Leaderboard

Tasks, steps, standups and days in, scored for the sprint. The podium is kept, so a place earned is a place remembered.

Scored from the work itself
Podiums and firsts kept
Badges for streaks and finishes

Messages from the admin

The admin writes to everyone, a role or chosen people. It lands in the bell and in Messages; an important one opens first at the next sign-in, and the admin sees who has read it.

Groups by role or process role
Important ones open on arrival
Read receipts, and a note when all have read

Team check-ins

Short check-ins a few days apart — the week’s weather, a battery, three words for the team, a shout-out — that tell the admin how people really are, with warnings before they become exits.

A minute or two, a few days apart
Anonymous by default
Trends and warnings for the admin

Notifications

Assigned, mentioned, a badge unlocked, leave decided, a shout-out — a toast the moment it happens and a bell that remembers.

No feed to watch
Each one opens where it points
Seen across every open tab

06Reports and operations

See where you stand

The project at a glance, reports that write themselves, and production feeding back into the backlog.

Reports and pulse

On track, at risk or off track — with reasons
Copy-ready for Slack or email
Momentum over the last two weeks

Project reports

Reports

The pulse of the project

On track

Momentum, blockers and quality from the work recorded today.

PulseEnd of dayWeekly

84Project health+4 since last week

Sprint pace83%On track

Ready work28+6 this week

Open blockers2Needs attention

Quality92%Evidence linked

Today’s signalDelivery is steady. Two blocked stories need a decision before planning closes.

Dashboard

Initiatives, readiness, flow and the sprint in one view, kept current as the work changes.

Readiness by initiative
Flow through the stages
Always current

Operate

Defects with their severity, incidents, readings and feedback from production — triaged, and turned into new stories when they are work.

Severity from your own list
Production readings against goals
Feedback becomes backlog

Goals

Daily, weekly, sprint, monthly, quarterly, yearly
Organisation, teams and people, aligned
Counted from tasks, stories and releases

Feedback portal

Anyone can report a bug, a gap or an idea against the part of Squid it touches, from any page. The admin triages it, and the reporter hears back.

Against the feature it is about
Triage with a note back
Nothing lost in chat

System status

Whether the database answers, when the last change and the last CI result landed, and what waits for review.

Database health
The agent’s last call
CI and review at a glance

Live in Squid

Meet Kraken, the assistant in Squid

1Is this right?It runs the rules and the gates on a story, a feature or a decision, and says plainly what holds it back and how to fix it.
2What do I do next?From the page you are on and what is waiting on you: one next step, then the few after it.
3Explain itAny gate, rule, lens or feature in Squid, in plain words, with where it comes from.
4Rewrite itA story, a criterion or a requirement, reworded to read well and pass the rules, as a suggestion you can use.

Kraken suggests. Your team decides. What comes after it

See it on your work.

Squid is opening to a few teams at a time. Leave your email and tell us what you use today.

Back to the tour