Healthcare
HIPAA
- Encrypt patient data at rest and in transit
- Log every access to health records
The spec-driven workspace
for your whole product team.
Plan, design, build and test software with AI, all from one Living Spec.
Start from an example:
Start free, no credit card needed.
By continuing, you agree to our Terms of Service and Privacy Policy.
Save up to 27% on token spend
SEE IT WORK
Change anything. Break nothing.
Your whole team works in the same Living Spec. Change a rule, and only the screens and code that depend on it update.
As your app grows, AI starts breaking what worked.
27% of all AI coding spend goes to fixing what breaks when context gets lost.
Single-chat AI toolsClaude Code, Cursor, Lovable
Rules get mixed up
The bigger the project, the more the AI juggles. It applies old rules, misses new ones and changes things nobody asked for.
Context lives in one chat
What the AI knows stays in one person’s session. Hand the work to a teammate and it has to be rebuilt.
Nobody sees what the AI decided
Data models, permissions and edge cases end up buried in generated code someone has to reverse-engineer.
OneSparkOne Living Spec
One spec holds the rules
Every feature's rules live in its Living Spec, and every change is built against it.
Context lives in the project
Your team and OneSpark read and update the same spec, across every session.
Every decision is written down
Plans, specs and docs show what's being built and why, before anyone signs off.
Better context = fewer tokens. Stop paying to fix what already worked.
Five phases. One Living Spec.
One Living Spec continually updates through every phase of the lifecycle, letting you ship and keep shipping as your project grows, never losing context between sessions.
Learn how spec-driven development works01 / 05
Plan
Get the PRD, roadmap, user roles and compliance requirements from your idea or brief. Refine anything in plain language before a line of code exists.
02 / 05
Design
Every screen in your brand. Click a screen or ask for a change, and edits stay in sync with the plan and the spec.
03 / 05
Build
Full-stack code built against each feature's spec, with its own schema and API contract. You see what each change touches before it runs.
04 / 05
Test
QA the build and flag an issue. OneSpark fixes it against the spec and pushes to staging.
05 / 05
Publish
Push to your GitHub. The code, the spec and the docs are yours.
Spec-driven development
The Living Spec: what every teammate and agent builds against
Every feature gets a Living Spec before any code is written. Your team, your client and our agentic system read and update it, so context stays complete as you add people, features and agents.
One feature, two readings
A product view for whoever signs off, and an engineering view for whoever maintains it. Nothing to keep in sync by hand.
Changes flow both ways
Reshape a feature and its spec updates. Edit a rule, state or endpoint in the spec, and the designs and code that depend on it follow.
You approve what moves
Every update is flagged for your approval. Nothing regenerates behind your back.
No AGENTS.md, CLAUDE.md or Cursor rules to keep current by hand. Static context files go stale. The Living Spec is written as the project changes.
Learn how spec-driven development worksSix products. Six completely different builds.
Same spec-driven flow every time, and nothing that looks like it came from a template. Real designs in your client's brand, laid out as a full web flow you can walk them through before anything is built.
No products in this category yet. Pick another filter to keep looking.
Visibility
See exactly what's being built. No black box.
Every phase, feature, design and decision is written down from the same spec, in documents your team and client can read, edit and share by link.
9 documents · one spec
Product requirements document
Written from the spec · always current
User personas
Written from the spec · always current
Who uses Cadence
Three roles, their goals and the pain points the product removes.
- Maya ChenClinic ownerGOALS· See utilization and revenue per therapist· Cut no-show ratesPAIN POINTS· Schedules live in three tools· No view of compliance statusMAIN SCREENSOwner dashboardReports
- Luis OrtegaPhysical therapistGOALS· Assign home exercise programs fast· Track each patient's progressPAIN POINTS· Visit notes written twice· Patients skip their exercisesMAIN SCREENSPatient chartPrograms
- Priya NairFront deskGOALS· Book around therapist and room availability· Fill cancelled slots from the waitlistPAIN POINTS· Double-booked rooms· Phone tag with patientsMAIN SCREENSScheduleWaitlist
Architecture overview
Written from the spec · always current
How Cadence is built
Services, how data moves between them, and the stack each one runs on.
CLIENTS Clinic web app Patient portal Admin console
API Auth & roles Scheduling Programs Billing
DATA PostgreSQL File storage Job queue
SERVICES Stripe payments Twilio SMS SendGrid email
TECH STACKNext.jsWeb and portalNestJSAPI servicesPostgreSQLPrimary dataPrismaSchema and migrationsRedisJobs and reminders
Business overview
Written from the spec · always current
Business at a glance
How Cadence makes money, who it sells to and where it stands.
- MODELPer-clinic subscriptionBilled monthly per location, with a per-therapist add-on.
- MARKETOutpatient PT clinicsIndependent and multi-site clinics with 2 to 40 therapists.
- POSITIONINGScheduling and home programs in one toolReplaces a booking app, an exercise app and spreadsheets.
- Starter$149/moOne location, up to 3 therapists
- Clinic$299/moUp to 10 therapists and the patient portal
- Multi-siteCustomCentral reporting across locations
- No-show rate under 8%
- Therapist utilization above 85%
- Programs assigned within 24 h
Industry and competitor analysis
Written from the spec · always current
Landscape and differentiators
What clinics use today and where Cadence wins.
| Option | Scheduling | Home programs | HIPAA-ready | Patient portal | Price |
|---|---|---|---|---|---|
| Legacy EMR suites | Yes | Partly | Yes | Yes | $$$ |
| Booking-only apps | Yes | No | No | Partly | $ |
| Exercise apps | No | Yes | Partly | Yes | $ |
| Cadence | Yes | Yes | Yes | Yes | $$ |
- Programs tied to each appointment
- HIPAA rules written into the spec
- Waitlist fills cancelled slots
Data models
Written from the spec · always current
Entities, fields and relationships
Six entities generated from the spec. Every feature reads and writes these.
Patient
iduuid
nametext
dateOfBirthdate
insuranceIdtext
Program
iduuid
patientIdPatient
exercisesjson
Appointment
iduuid
patientIdPatient
therapistIdTherapist
roomIdRoom
startsAttimestamp
statusenum
Therapist
iduuid
nametext
specialtytext
clinicIdClinic
Room
iduuid
clinicIdClinic
nametext
Clinic
iduuid
nametext
timezonetext
Infrastructure diagram
Written from the spec · always current
Environments, services and integrations
Every change moves from development to staging to live.
Developmentlocal
Web · Next.jsAPI · NestJSPostgreSQLRedis · jobsFile storageStagingpreview
Web · Next.jsAPI · NestJSPostgreSQLRedis · jobsFile storageLivelive
Web · Next.jsAPI · NestJSPostgreSQLRedis · jobsFile storageINTEGRATIONSStripeTwilioSendGridSentryGitHub Actions
- Daily backupsKept for 30 days
- Uptime checksEvery minute, alerts to Slack
- Encrypted at restDatabase and file storage
Test strategy
Written from the spec · always current
Coverage, test types and QA flow
Every acceptance criterion in the spec becomes a test that runs on each build.
- Unit82%412 tests
- API contract64%96 endpoints checked
- End-to-end18 flowsBooking, waitlist, programs
- Spec rule
- Test written
- Runs on each build
- Flagged in Test
- Fixed against the spec
- Unit
- API contract
- End-to-end flows
- Accessibility · WCAG 2.2 AAA
- Visual match to design
Security and compliance
Written from the spec · always current
Requirements, access rules and data handling
Written into each feature's spec and checked on every build.
HIPAARequiredEncrypt patient data at rest and in transitLog every access to health recordsSign a BAA with the hosting provider
SOC 2RecommendedRole-based access on every screenAudit trail for admin actions
GDPRRequiredPatients can export or delete their data
| Access rules | Records | Schedule | Billing |
|---|---|---|---|
| Owner | Allowed | Allowed | Allowed |
| Therapist | Allowed | Allowed | No access |
| Front desk | No access | Allowed | Allowed |
| Patient | Allowed | No access | No access |
DATA HANDLINGHealth records kept for 7 yearsExports and deletions loggedBackups encrypted, 30-day retention
Edit any document.
- Document changed
- Specs updated
- Software decisions updated
Compliance
HIPAA, SOC 2 and GDPR requirements, written into your spec
Building for healthcare, finance, education, government or enterprise clients? Choose what your product has to meet while it's still a spec. Roles, permissions, data handling and storage rules all come out of the same plan, instead of being bolted on after someone asks.
- Enterprise and B2B
SOC 2
- Role-based access on every screen
- Audit trail for admin actions
- EU users
GDPR
- Consent before any tracking
- Users can export or delete their data
- Accessibility
WCAG 2.2 AAA
- 7:1 contrast on all text
- Every action works by keyboard
- Required
- Recommended
- Optional
Each requirement is marked Required, Recommended or Optional, with the reason. Most AI app builders leave this until after the app is written.
Built for whoever has to answer for it.
Agencies & consultancies
One workspace, every client build kept separate.
Engineering teams
One spec your whole team and every AI session share.
Product managers
One spec everyone works from.
Founders & freelancers
Deliver like you have an entire technical team.
Works with the tools you already use
Connect the services your product needs, like payments, auth, monitoring and email, right from the plan.
- Stripe
- GitHub
- Slack
- Sentry
- OpenAI
- Twilio
- SendGrid
- Cloudflare
- Vercel
- Firebase
- Discord
Your product is yours. All of it.
The idea you type in, the spec, the designs, the documents and the code all belong to you. Nothing you build here shows up in anyone else's product.
You own everything it makes
Spec, docs, designs and code. Push to your own GitHub any time and keep working anywhere.
Your idea isn't training data
Your projects are not used to train models. What we store, and for how long, is in the Privacy Policy.
Isolated by project
Every project runs in its own workspace, separated from other projects.
Start free with no card. Add your team when you're ready.
Free: plan, design and chat with your project. Building and testing the app needs Pro.
Pro
$20/mo
- 500 credits a month
- Full build and every document
- Push to GitHub, no branding
- For founders and freelancers
Team
$25/seat/mo
- 500 credits per seat, pooled
- One shared spec for the whole team
- Roles and client viewers
- For agencies and dev teams
Save 20% with annual billing. See full pricing
Questions, answered
A product requirements document describes what you're building, who it's for and how each feature should work. OneSpark writes yours from a short description or client brief, then keeps it in sync as the project changes.
Spec-driven development means writing down what you are building before any code is written. In OneSpark that spec is the Living Spec: it drives the design, the build and the tests, so the AI builds against a plan instead of guessing. Your whole team works from that one source, and every change goes through the spec first.
The spec for each feature, with a product view and an engineering view. Your team and our agentic system read and write it, and it updates as the project changes.
Yes. Your team, your client and every AI change work from one shared spec, with roles for owners, editors, viewers and client reviewers.
Those tools start from a prompt and keep context in one person's chat. OneSpark starts from a spec the whole team shares, shows you what every change affects, and writes compliance requirements in from day one.
Vibe coding builds from a chat, one prompt at a time, so the AI guesses as the app grows. Spec-driven development writes the plan first and builds every change against it, so what worked keeps working.
Only what the change touches regenerates, and only after you approve it. Everything else stays exactly as you shipped it.
Yes. Our own software agency delivers every client project in OneSpark. Keep each client build separate, use your own branding on paid plans, and share the spec and docs with your client by link.
OneSpark writes HIPAA, SOC 2 and other requirements into your spec and builds against them. Full compliance also depends on your hosting, contracts and how you operate the app.
GDPR, HIPAA, SOC 2, WCAG 2.2 AAA, CCPA, COPPA, FERPA, ISO 27001 and FedRAMP. Choose the ones your product has to meet, and their requirements are written into your spec.
You do: the spec, the documents, the designs and the code. Push it to your own GitHub any time.
Plan, design, build, test and publish to GitHub, with generous limits and a direct line to the team.
Beta
Plan your next project in 7 seconds.
OneSpark is young and moving fast. Early builders get generous limits, a direct line to the team, and a real say in what we build next.
- Early access to every new capability
- Generous build limits
- Your feedback shapes the roadmap