Built for everyone who ships your product

Where your whole team can safely build the product.

PMs, designers, support, and engineers ask in plain language. Gently works safely in an isolated copy of your app, then returns a working preview and a pull request your team can review.

Request access See how it works

From request to reviewed change

One thread · one safe sandbox

PMEng
  1. 1

    Ask in plain language

    “Let admins invite their team from a CSV.”

  2. 2

    Gently works in a safe copy

    Your real app runs in an isolated sandbox, away from production.

  3. 3

    Review the result

    Open the working preview, watch the recording, and review the pull request.

Collaborative Wireframes Live preview Recording Pull request
Who it’s for

Everyone works in the same thread, while engineering keeps the normal review and approval process.

Product

Settle the feasibility fight

Ask whether the roadmap item is a config change or a quarter of work. Get a cited answer from the real code before the meeting ends.

Support

Find the root cause

Paste a customer’s error. Gently searches the app’s logs, points at the line that caused it, and can fix it in the same thread.

Design

Adjust the real flow

Reorder the onboarding steps, reword the empty state — safely, in the thread’s own sandbox — and review it live at a preview URL instead of guessing from a mockup.

Engineering

Offload the grind, ship faster

Hand off the flaky-webhook log chase and get back a root-caused PR with a repro recording. Keep the architecture; skip the busywork.

How it works

Start simple. Gently brings in the technical depth only when the work needs it.

  1. 01

    Start with the outcome

    Describe the customer problem, product question, or change you need. Teammates can add context in the same thread.

  2. 02

    Watch it work on the real app

    Gently reads the connected product context, runs the app in a fresh sandbox, and checks the change in a real browser.

  3. 03

    Hand engineering the evidence

    The thread returns citations, checks, a live preview, a recording, and a pull request ready for normal review.

See a full example thread Bulk team invites from a CSV
Let admins bulk-invite their team from a CSV
northwind / web + api + worker
Sandbox live
M
MayaImplement

Enterprise trials stall because admins invite people one by one. Can they upload a CSV and invite everyone at once?

S
Sam

One constraint from engineering: invites go through the worker queue, so batch them there — and keep the 500-row cap the rate limiter expects.

Ask, plan, or build anything…Auto

The detailed thread keeps every participant, source, check, preview, recording, and pull request together for anyone who needs to inspect the work.

Safe by design

Gently can understand and run a complex product while keeping production and the final shipping decision in your team’s hands.

Production stays untouched

Every thread gets a disposable, isolated copy of the app. A reviewed pull request is still required before anything ships.

Proof you can open

Reviewers get a live preview, screenshots or a browser recording, and the checks that ran — not just a generated diff.

Built for the whole system

Web apps, APIs, workers, databases, monorepos, and multi-repo products can run together in the same sandbox.

FAQ
Is it safe?

Every thread gets its own isolated sandbox — a disposable copy of your app, never the real thing. Nothing reaches production without a pull request reviewed like any other code. Your code stays in GitHub and sandboxes are destroyed after the run.

What guardrails does it have?

Autonomy is opt-in. Roles decide who can ask questions and who can propose changes, granted per team. Every action — files touched, tests run, commits made — lands in a trail you can audit.

Can non-engineers really get things done?

Yes. Questions get cited answers from the real code, no engineer needed. Changes come back as a PR with a preview and a recording, and it goes through normal code review — the same path your engineers’ own Gently changes take.

Isn’t this just a tool for PMs?

No — engineers are heavy users, not gatekeepers. They hand Gently the log chases, flaky repros, and small fixes that eat afternoons, and spend the time on work that needs them. Everyone works the same way — a thread, its own sandbox, evidence — and nobody is stuck reviewing at the end of a pipe.

How accurate is it?

More accurate than tools that only read code, because Gently runs yours. Browser capture feeds console errors and failed requests back mid-build, it searches your app’s logs and fixes what it finds, and it verifies the changed flow in a real browser before handing over. If verification fails, you see that too.

Will it work on our complex app — monorepo or multi-repo?

That’s the expected case. A project connects one or more repos — web, API, workers — and runs them together in one sandbox, so a single thread can read and change code across services. Legacy code is the point, not the exception.

Will it work with our database?

Yes. Sandboxes run your services with their databases, seeded for the sandbox and never pointed at production data, so changes are made and verified against a working stack.

How does pricing work — and what stops a surprise bill?

Usage-based from $20/month with no per-seat fees, so the whole team — engineers included — can be in from day one. Admins set budget caps and alerts; when a cap is hit, runs pause instead of spending through it.

How do we get started?

Gently is invite-only while we onboard teams carefully. Request access, connect the repos that make up your app, and invite everyone — start with the questions your team already asks each other every week.

Connect the app once, invite the whole team with no per-seat fees, and let the first thread show its work. Gently is invite-only while we onboard teams carefully.

Request access