Engineering. From planning to release.
Projects, backlog, delivery, QA, releases, resources and the client context in one working cycle.
Module status
No module under this team is waiting for its suite to start — every one of them is sold and available today.
Synapse is a layer of the platform rather than a sixth module under this team: it comes with every paid plan and gives this team’s work the context of the rest of the company.
When the cycle is cut
One requirement. The road from it to the customer is cut into tools.
A requirement lands in a tracker, the work happens somewhere else, the test case lives in a separate test-management tool, and the client asks about status by email. Every seam between them is stitched by hand — and it is on the seams that “done” stops meaning “verified”.
Four of those seams are listed on Companion’s own page, as the work that stops being work. Here they are, in the same words:
- Copying a client request into a ticket by hand
- Reconciling what was built against what was asked for
- A separate test-management tool that the agents cannot see
- Status updates written to tell a client what the system already knows
Stated on the page for Companion
Below is the same road without those seams: from the requirement that arrives from product, to the customer who sees the result in their own workspace.
What this team does in Sintora
Runs as many agents in parallel as the job needs — on a build server of your own.
Plans and delivers in agile workflows: boards, roadmap, backlog and built-in QA.
Runs test cases, plans, executions and defects, linked to the sprint.
Shows who is free, who is overloaded, and what that does to the dates.
From the requirement to the customer
This is where the chain reaches the customer, and this team is its last link
The chain on the Solutions hub is linear: one team hands the work to the next. The team has more edges than that, and the full list is in the block below. What is shown here is the other thing: the object that crosses the boundary of the department, and the module it lands in.
What arrives
ProductRequirement + context
Where it lands
A priority off the roadmap becomes a backlog line and a card on a board — in the same module the sprint will run in, and the one the test management already sits in.
ProjectsWhat happens inside
Kanban and Scrum boards, the roadmap and the backlog — the plan sits where the work will run, and where the built-in test management already is.
The date is not promised blind: capacity, allocation across projects and teams, overload detection and plan against actual — in one view.
Shown by Resource Planning ProjectsA task fans out across as many agents as the work splits into — in parallel, inside the workspace’s own isolated environment, where it is built, run and tested.
The limit is the shape of the work and the size of the environment, not a per-agent line on the invoice. And every task carries the request it came from.
CompanionTest cases, plans, runs, defects and coverage — linked to the sprint, with quality reporting over them. And what the agents build is checked against the same test cases your QA team wrote, rather than against criteria an agent set for itself.
Machine-written work is verified by the same criteria human-written work is, which is the difference between output and delivery.
QA ManagementHere “Release” means the change has been checked against the test case that proved it, the client’s request is closed, and the milestone and the monthly report in their workspace have updated. That is the end of the cycle from the client’s side.
And it means exactly that: the platform ships no release manager — no release planning, no version management, no deployment history. The word here is about a change reaching the customer, not about what rolled it out.
Client PortalWho gets it
CUSTOMERRelease + what changed
Where they see it
The client logs into a branded workspace of their own on your domain and sees the progress, the milestones, the documents, their own requests and the monthly report — without anybody writing them a status update.
Client PortalThe screen this team opens
Task from the board
DEV-418 · Session is not extended after a token refresh
MCP · Wiki
2 pages from the “Platform” space added to the context
npm run check
0 errors
MCP · Projects
DEV-418 → Done, comment added
DEV-418
DoneSession is not extended
Companion
Session refresh fixed, checks green. Moved it to Done.
Recorded for the day
- Agent time
- 38 min
- Commits
- 3
- Lines
- +128 / −54
The modules under this team
Each one is a module of the platform with a page of its own. The team works inside them, not alongside them.
The workspace where the work gets made: as many agents in parallel as the job needs, on your own build server, wired into the projects and test cases the Developer Suite runs on.
Open the modulePlan, build and deliver software using Agile workflows with integrated quality management.
Open the modulePlan, execute and monitor software testing throughout the delivery lifecycle.
Open the moduleA branded workspace the client logs into: project health, milestones, documents, requests and the monthly report — on your domain, under your logo.
Open the moduleWho is free, who is overloaded and what that does to the dates — capacity, allocation across projects and plan against actual in one view.
Open the moduleAgents, and the perimeter
What an agent can reach, where it runs, and whose account it runs on
Three questions an engineering team asks before any demonstration. The answers below come from the same pages they are published on for a buyer.
An isolated environment
Each workspace gets its own environment to build, run and test in, so agent work does not queue behind a shared runner and does not touch anyone else’s.
Your own provider account
Several model providers run side by side, each named openly, and the account with the provider is yours. Each agent runs on whichever model suits its task. Sintora does not resell inference, so nobody is routing your work through someone else’s margin.
Permissions
The context and the tools available are decided by the user’s permissions, the modules that are switched on, and the workspace configuration.
What reaches it
Companion reaches the platform through the same MCP server every other client uses: projects and tasks, test cases and runs, client tickets, documents and the company’s shared context.
This team’s modules are exposed to agents as MCP tool groups — the same ones any other client of that server uses. This is the inventory from the developers page, not a list assembled for this one:
Module · MCP group · how many tools it holds
And the largest group in the whole inventory belongs to this team: Test management 26 tools out of 142 · QA Management
Without a group of its own: Resource Planning
Companion is one client of that same MCP server rather than a private channel into the platform. The full tool list, and how to connect a client of your own, are on the developers page.
For developersAnd here is how the modules sit together — in the words of Companion’s own page, about the whole suite rather than only this team’s:
Companion is where the work is made; the Developer Suite is where it becomes a business. Projects holds the boards and the backlog, QA Management holds the test cases the agents are checked against, the Client Portal is the client-facing side of the same records, and Time & Billing and Resource Planning turn the result into capacity and an invoice. Synapse gives every agent the company’s own context — past decisions, documents, calls, clients — rather than only the repository, and everything an agent does is written back into it.
The same cycle, from the other side
Most often the work arrives not off a roadmap but from a customer for whom something broke
The chain on the Solutions hub is linear and knows one neighbour — Product. But this team has two sources of work, and the second is the queue of Operations. Here is that path, already published as a scenario — from a support ticket to what the customer sees in their own workspace.
From bug report to release
The modules it passes through
Suites 2 Modules 4 And no export between them.
It ends where the cycle above ends: the ticket closed against the test case that proved the fix, and the customer seeing it in their own workspace. What «release» means here is stated above, on that stage’s own card.
Open the scenarioNo team works on its own. Here is who hands this one its context and who takes it on — every link goes to that team’s page.
Where the work arrives from
- Product — the priorities and the roadmap
- Operations — work out of the queue
Where it goes next
- Customer Success — what shipped, and what changed for the customer
- Finance — the hours and the actuals
- People & HR — the roles and the skills that are needed
From planning to release.
We will show how this team works in Sintora — on your processes, not on demo data.