What’s new at Serras.

Fewer steps between the work

Symphony now prepares a build plan with one call instead of three. It publishes your files in groups of up to 128, and it records finished tasks without extra AI steps. So less of each run goes to bookkeeping. Upload keys go straight to your machine and never pass through the AI. If a connection drops, the run picks up where it stopped and uploads nothing twice. Every review and approval stays the same. New runs use this after you update.

Large plans save much faster

In our tests, saving a plan with 1,758 changes now takes about a fifth of the time and less than half the memory. Plans of that size that could run out of time before now finish well inside the limit. A plan still saves all at once or not at all. You do not need to update anything.

More on Waypoint

Two more reviews for video when you approve by hand

In Manual Approval, you review each new piece of work before the next step uses it. Video production now adds two of these reviews. First, you read the full text of every shot and narration line before any video is made. Then, you check the final list of verified files before the film is uploaded. Auto mode does not change.

More on Video production

Long runs stay open while they work

A run that is still working now stays open for as long as it needs, with no time limit. Serras closes a run only after six hours with no activity, and you can then restore that same run with its approvals, progress and cost record. An update you install during a run does not change the version that run uses.

Change the plan without restarting the build

When you approve a change to the plan while a build is running, only the tasks that changed, and the work that depends on them, run again. Finished work that the change does not touch is checked and kept, so the build does not start over.

Choose how strict the build review is

The independent review of each build task now has three settings: balanced, which is the default, strict and advisory. You also choose how many repair rounds it can try, from none to five. Style preferences never force rework. Security problems and serious defects always block the task, in every setting. When the repair limit is reached, the task waits for your decision and is never marked as passed.

Clear narration over music

Video production now measures every narration line against the music and lowers the music where a line needs room, so each line stays easy to hear. Text in a source picture is read back and checked before any video is made from it. Long films are backed up in parts, and every part is checked when the film is put back together.

More on Video production

Early estimates count cleanup and deployment once

An estimate adds a 10% reserve for final cleanup and deployment. When the plan behind an early estimate already prices both of those stages, the reserve is now 0%, so the same work is not counted twice. If only one of them is priced, the estimate stops and says so. Pitch decks built from the estimate show the same figure.

Cost reports that add up

Cost reports now count each piece of work once. This holds when a worker reports its usage more than once, when a run moves between Claude Code and Codex, and when a long session is summarized to save space. Estimated numbers stay marked as estimates, and missing numbers show as missing, never as zero.

Video production

A new workflow turns a brief into a narrated film in your brand. You approve a storyboard with a picture for every scene before any video is made, then approve the cut before music is added. Your logo, titles and product screens are set in code, so they are always exact. The Serras film on our home page was made with it.

More on Video production

Each stage starts from a brief

Each stage now starts from a short brief written by the stage before it. The brief points to the exact source material and decisions the next stage needs, so less of each run goes to finding its place.

Builds keep going around blocked work

When a task is missing something it needs, such as a tool, a file or a setting, only that task and the work that depends on it wait. Independent tasks keep building, and a setup check that already passed does not run again.

Large plans reach Waypoint in one step

When a workflow such as Delivery Plan sends 25 or more changes to Waypoint, they now go as one package. All the epics, tickets and links are saved together, or none are, so a plan never arrives half done. If the connection drops, sending again does not make copies. Smaller change sets still go one at a time.

More on Waypoint

Podium is live

Podium, the portal where your clients follow delivery, is now live on the web. Clients see their projects, the updates you publish and the work you release in one place, without waiting for a status meeting.

More on Podium

Sign in with your Serras account

Clients choose “Continue with Serras” and sign in with the account they already have, so Podium does not add another password.

Clients see only what you share

A client sees only the projects shared with their organization, and only the updates your team chooses to publish. Work in progress and unshared projects never appear, not even in counts.

Honest project status

The project overview shows where work stands only from sources Serras can trace, with the time it was last checked. When something is unknown or may be out of date, Podium says so instead of guessing.

Releases your clients can open

Each release shows the exact version you shared. Clients can preview it in the browser, download it or share a link with a colleague. Every open checks access again, so a shared link never carries anyone’s sign-in.

Quick mode for Design

Design can now start from a single concept, or from a mockup you already have, instead of three competing concepts. You approve the concept, then the refined version, before the rest of your app is designed. The full three-concept exploration is still there when you want it.

Estimate a project before full design

An early-estimate mode designs a sample of your key screens, accounts for every other screen in scope, and turns the result into a work plan and an estimate you can review before you commit to full design. When you go ahead, full design builds on the approved sample instead of starting over.

Brand concepts built from your product

Brand concepts now start from specific facts about your product and audience, not generic themes. When all four are ready, choose one straight away or ask for a blind critique of each first. The logo you pick is traced into a clean SVG file, so it stays true to the version you approved.

Every stage reads your source material

Every stage, from discovery to implementation, now reads the original material you supplied, not only summaries from earlier stages. Each stage records what it read, and flags any file that was missed or changed during the run.

Pick up where you left off

Run the same workflow again after an interruption and it continues from its last checkpoint, keeping finished work and your approvals. After an update, one step refreshes each project without rerunning setup or touching your approved work.

Builds wait out busy AI providers

If your AI provider reports that it is overloaded, implementation now slows down, waits and retries until the provider recovers. It also sets how much work runs at once from your machine’s capacity, and groups related tasks so they share setup work.

Clearer decision prompts

When a workflow needs your decision, the window now names the project, sums up the choice in a few key points, and gives you buttons that open the work you are reviewing.

Narrated video for pitch decks

The pitch workflow can now write a spoken script for each slide, voice it with your own ElevenLabs account, time every slide to its audio, and export the deck as a synced video. Before any audio is made, you see the character count that sets the cost, and you approve it.

The top model for creative work

Brand and Design now send creative work, such as visual direction, design and critique, to the top model on your plan. Routine extraction and checks go to the next model down, so they use less of your plan. Cost reports price each step by the model that ran it.

Progress counts only saved work

Build progress now counts only the tasks a build has actually saved. A run can no longer show itself as complete when its tasks were never recorded.