Skip to content

For web developers and agencies

Stop being texted at midnight.

  1. Messages

    Maja · Studio Nord

    Hi! Can you change our opening hours on the site?

  2. Messages

    Maja · Studio Nord

    Also, the homepage photo is old, can you use the one from our About page?

  3. Messages

    Maja · Studio Nord

    And the phone number in the footer is wrong!! It's 01 234 56 78

  4. Messages

    Maja · Studio Nord

    Sorry for the late message 🙈

  5. Rounds

    Studio Nord

    Maja changed the opening hours herself. The photo and the phone number are written down for your next round.

  • Pull requests, never pushes
  • Clients never need GitHub
  • Hosted in the EU

What just happened?

The next morning, Studio Nord's change log in Rounds: what went live, and what waits for you.

studio-nord.siChange log

Last night

  1. Live

    Maja changed the opening hours herself

    A text you marked as hers: she edited it on the page and it went live. Nothing for you to review.

  2. Next round

    Maja asked for the About page's photo on the homepage

    She pointed at the photo and said, in her own words, which one goes there instead. Written down for your next round.

  3. Next round

    Maja sent the right phone number for the footer

    01 234 56 78, in place of the wrong one. The footer is not marked as hers, so this waits for your next round too.

  4. Coming up

    Pull request

    Round 3: both requests in one pull request

    You review it and merge it. Apart from the texts you marked as hers, nothing reaches the live site without you.

See it in action

What your client does on her own site, and what reaches you.

  1. Maja opens the panel on her own site: a shortcut and her password.
  2. She points at the opening hours and changes them right on the page.
  3. For something bigger, she describes it in her own words.
  4. Her change goes live, and the rest waits for your next round as one pull request.

One panel, two people

You stay in charge of the code. Your client stays in charge of their words.

You, the developer

Requests you can act on

  • Written down, on the element they mean. Never a screenshot in a chat.
  • Batched into rounds at the pace you agree, not a trickle of messages.
  • Each change a pull request with the request attached. Nothing goes live without your merge.

Your client

A website they can look after

  • A shortcut and a password open the panel on their own site. No accounts, no tickets.
  • Texts you mark as theirs they change right on the page, any time, for free.
  • Anything else they point at and describe in their own words.

How it works

  1. Point and describe

    On their own site, your client presses a shortcut, enters their password, points at the thing and writes what they want. No tickets, no screenshots in a chat.

  2. Collected into rounds

    Requests wait for the next round, at the pace you agreed.

  3. Delivered as pull requests

    Each change arrives written down: the page, the element, the request and a proposed change, as a pull request you review. Nothing reaches the live site without you.

Rounds for APIs

The same care for the code behind the site

Providers retire API versions, shut down models and rename what their SDKs export. Rounds for APIs reads a site's own repository and shows where its code still uses something deprecated, retired or outdated.

First providers

  • Stripe
  • OpenAI
  • Anthropic
  • Vercel AI SDK
  • Next.js
  • What it reads

    Your site's repository, through the Rounds GitHub App: package lists, lockfiles, configuration and source. The report writes nothing, and Rounds keeps no copy of the files.

  • What you get

    Every finding, where it is in your code, and a link to the source it rests on: a deprecation notice, a security advisory, a migration guide or release notes.

  • How a change arrives

    Only where the fix is mechanical – a patch or minor upgrade, a rename, a retired model to its named successor – and only with your recorded permission, for that change and the files it names. It arrives as a pull request, never a push, and your repository's own CI checks it.

  • What it never does

    Rounds never merges, never leaves a branch without a pull request, and never touches workflows, .env files or build images. It reads only the names and results of your checks, never their logs. No one at ScAIentist® looks at your code, except when you ask us in writing to help with a specific problem, and then only the files that problem concerns.

The report is built, and opens to everyone when accounts arrive; they are on their way. Letting Rounds make changes is built too, and will be switched on first for a few design partners.

Become a design partner

Or write to info@scaientist.com: which of these providers your sites use, and how many repositories you look after.

Pricing

Per site. You choose how often a round opens. Whatever your clients edit themselves is always free.

  • Yearly

    Free

    1 round a year

    For sites that rarely change.

    • Your client edits their own texts, any time
    • Everything else arrives once a year, as a pull request
    • Move to a faster pace when you need one
  • For agencies

    Studio

    €389.70 per round

    Up to 20 sites, a round every 3 months.

    or €1,299 a year, paid up front

    SEO fields includedPage titles, descriptions and link previews, on every site.

    You pay when a round opens, never in between.

    works out to €129.90 a month

    Below 13 sites the per-site plans come out cheaper than Studio, and we will tell you so.

Compare every cadence
PlanRounds a yearBilled per roundPaid yearlyPer month, on average
Yearly1 round a yearFree––
Every 6 months2 rounds a year€47.40€79€7.90
Every 3 months4 rounds a year€44.70€149€14.90
Every 2 months6 rounds a year€39.80€199€19.90
Monthly12 rounds a year€29.90€299€29.90

More sites, lower price

  • from 3 sites: −20 %
  • from 10 sites: −30 %
  • from 25 sites: −40 %

Applied automatically across all your sites, whatever their pace.

Add-ons

  • SEO fields (page titles, descriptions, link previews): €4.90 per site a month, included in Studio.
  • An extra round when something cannot wait: half of what a round costs on your plan, once a year.

Prices in euros, excluding VAT.

Online sign-up is on its way. Until then, write to us and we will set up your first site with you.

What a round is, and is not

A round is

  • A batch of changes, delivered together as one review.
  • Written down: what, where and why, in your client's words.
  • Paced: the next one opens on a date you both know.

A round is not

  • A hotline: faults are fixed for free, outside the rounds.
  • Unlimited development: a redesign or a new feature is quoted separately.
  • A way into your code: clients never get access to the repository.

Built to be trusted with client sites

Pull requests, not pushes

Every change is a pull request on your repository. You review it and you merge it.

No keys for clients

Clients get a password for the panel on their site, never access to your code or your hosting.

Hosted in the EU

Rounds runs in Frankfurt, and requests are stored in an EU database run by ScAIentist®.

Signed-in apps too

For internal tools, isolated mode seals the panel off: it never acts with the user's rights and sends only what is needed to find the element.

Questions

Do my clients need a GitHub account?

No. They get a password for the panel on their own site. GitHub is only where you review and merge.

Which websites does it work with?

Sites whose code lives in a GitHub repository, such as Next.js and other static or server-rendered sites. WordPress is not supported yet.

Can a client break the site?

No. They can only change the texts you mark as theirs, and every other change is a pull request you review first.

What about my own mistakes?

A fault in your work is fixed for free and never waits for a round. Rounds are for changes, not for repairs.

Where is the data kept?

Rounds runs in Frankfurt, and requests and the change log are kept in an EU database run by ScAIentist®. The privacy notice says exactly what is kept and for how long.

What does it cost to try?

Every site can start on the yearly plan, which is free. You start through checkout: a card is saved, and nothing is charged on the free plan. You move to a faster pace only when your client needs one.

Start with one site

Write to us with your sites' addresses and how often your clients ask for changes. We will set up the first one with you.

Get early access