Keep control as delivery moves faster.
Decisions, checks, and history stay attached to the work. You can always see what happened and why.
How do we stay in control?
You see and approve the important choices in Studio. Symphony carries them forward.
What do clients receive?
Podium shows clients the project’s progress, the decisions that need them, and the work you release, with a notification when something new is ready.
What is patent pending?
Two things: keeping a traceable history of AI work, and getting an independent model’s assessment before a consequential action runs. Both applications were written with Symphony.
How is the work validated?
Validation connects requirements to design, features, and functional behavior. Findings feed back into fixes and further checks, with evidence available for review.
Covers: Symphony delivery workflows
Supporting material: shown as a sample
One pass is shown, as a sample.
Who sees what we share?
What you send through this site goes to the Serras team and nowhere else. It is encrypted on the way and at rest. If we do not end up working together, we delete it after 30 days.
Covers: messages sent from this site
Supporting material: on this site
Read how we handle your message
This site has no accounts. Nothing you type is kept anywhere but that message.
How do we get started with Serras?
Start with a demonstration, discuss a delivery project, or explore a venture partnership. We will connect you with the right path for your team.
Covers: Symphony, Studio, and Podium
Supporting material: on this site
Podium access is tied to your project.
Your delivery, laid bare.
What you own, what is recorded, and what you keep.
- Your code lives in your repository, on your account.
- The record of each stage lives there too: the brief, the scope, the designs, the plan and the checks.
- Every decision is logged with who made it.
- Every check traces back to a requirement you approved.
- Every fix stays beside the flaw it fixed. Nothing is quietly patched.
- Your main AI work runs in your own Claude Code or Codex account.
- Lessons from your project stay with your project. A lesson is shared across projects only when it carries no client names, code or data.
- If you leave, you keep the code, the documentation, the designs and the record.
Where your data goes.
A plain account of what runs where.
- Stays with youYour accounts
- Claude Code or Codex: the main AI work
- Your repository: the code
- The recordSerras
- The delivery record: runs, decisions, lessons, files
- Hosted in the United States
- Supporting callsSupporting providers
- Lesson search, images, second opinions, typed checks
- Narration and email, when you use them
- The main work runs in your account.Symphony’s workers run inside your own Claude Code or Codex account, under your provider’s terms.
- Serras keeps the delivery record.Runs, tasks, decisions, lessons, usage and the files each stage produces are stored in Serras’s database and file storage on Supabase, in the United States. Serras’s web apps run on Vercel, in the United States.
- Some supporting steps use Serras’s own provider accounts.Lesson search and second opinions (OpenAI), brand and design images and second opinions (Google Gemini), typed checks of plans (TypeSafe), narration when you ask for it (ElevenLabs), and research searches (Serper, SerpAPI and Google).
- Email goes through two senders.Weekly client status emails go through SendGrid. Messages from the demo form reach Serras through Resend.
How Serras uses AI.
- Serras does not train or fine-tune AI models on your data.
- Your main AI work runs on your own provider account, under your provider’s terms.
- Serras’s supporting AI calls go through each provider’s business API.
- Estimates use only anonymized, combined figures from past projects.
Report a security issue.
Email security@serras.ai.