SaaSWish

YOUR NEXT CHANGE STARTS HERE

Move the work forward.
Stay close to the code.

Meet SaaSWish, your autonomous software engineer. Hand off a task, follow the work in its own sandbox, and review the changes before they become your next pull request.

Get started

Create an account in a minute. No credit card needed.

Real session, sped up
● ● ●SESSION / Improve the health endpointIn progress

THE PLAN

  • Read the route and existing tests
  • Add a health response
  • Run checks and inspect the diff
  • Open a pull request for review
Keep the response small.
Keep the change reviewable.

SHELL

$ npm test -- health
✓ health responds with status 200
✓ response includes service status

$ git diff --stat
 server/health.ts | 2 +−

CHANGES / health.ts

− return response.send('ok');
+ return response.json({ ok: true });
Illustrative session · your review comes next

FROM INTENT TO A REVIEWABLE CHANGE

A clear path through the work.

  1. 01

    Describe the task

    Bring the bug, the feature or the maintenance job. Add the repository and the context that matters.

  2. 02

    Start with a plan

    The agent writes a plan so you can follow its direction and steer it as it goes.

  3. 03

    Watch it work

    It works in its own sandbox with a shell, browser, editor and git. Inspect the workspace along the way.

  4. 04

    Review the diff

    Review the changes and have the agent open a pull request. Keep the discussion attached to the work.

ASYNCHRONOUS BY DEFAULT

Hand it off.
Come back to a pull request.

Start several sessions and get on with your day. Each one works in its own sandbox, in parallel, and only asks for you when it needs a decision.

  • Many tasks at once

    Run sessions side by side, or let one session split a large change across child sessions.

  • Pulled in only when needed

    Questions, approvals and finished work land in your Inbox or Slack.

  • Work while you sleep

    Schedules start recurring tasks, such as dependency updates, overnight.

Fix the flaky sign-in test

Pull request opened

Upgrade the app to Node 22

Running checks · step 4 of 6

Add CSV export to reports

Waiting for your answer

Weekly dependency updates

Scheduled · Mon 02:00

Idle sandboxes sleep while they wait, so waiting costs nothing.

MORE THAN A REPLY

The tools to carry a task through.

From a small fix to a multi-part change, keep the work and its context together.

A workspace you can watch

Follow a session through its live shell, browser and editor. Inspect the files and changes as the work unfolds.

Room to try another path

Checkpoints save workspace files before changes. Restore in one click, with Undo if you change your mind.

Keep consequential steps in view

Approve risky commands, scan for secrets before a push, or use step mode to approve each plan step.

Split the work, keep the thread

Parallel helpers tackle parts of a task. Child sessions handle separate streams and report back to the parent.

Carry your working habits forward

Share Knowledge across your organization, reuse playbooks with macros, and keep durable preferences in memory.

Make recurring work routine

Schedule prompts with cron. Repeat code scans daily or weekly and see newly reported findings.

Meet work where it arrives

GitHub PRs, a review bot and a CI fix loop. Connect Slack, Microsoft Teams, Linear, Jira and MCP servers.

Build your own entry points

Create and steer sessions through the REST API, or connect an MCP client to SaaSWish as an MCP server.

WORKSPACE, NOT WAITING ROOM

Pay only while it works.

Cloudflare sandboxes sleep when idle and cost nothing while stopped. Workspace files are kept for wake-up; running processes start again.

SaaSWish starts the sandbox while you type, so it’s usually ready when you send. No need to keep a machine running just in case.

Idle → asleep
Next task → workspace restored

Files kept. Ready for the next idea.

BUILT FOR YOUR BOUNDARIES

Your team’s controls.
Your team’s work.

Connect identity, manage access and keep a record of what happened.

Identity and provisioning

OIDC single sign-on, two-factor / MFA enforcement for every member, and SCIM 2.0 user provisioning.

A record you can use

An audit log with CSV export, plus GDPR data export and account deletion controls.

Secrets stay out of the conversation

AES-256-GCM encryption at rest. Saved secrets are injected only as sandbox environment variables and redacted from output. Server credentials never enter sandboxes.

USAGE, WITH GUARDRAILS

Pay for the work, not idle machines.

Usage is counted in Dev Units (DU), which cover model usage and sandbox time: 20 minutes of a running sandbox is 1 DU. Sleeping sandboxes use none.

Pay as you go

$1.98 / Dev Unit

Prepaid credit packs of 10, 50, 200 Dev Units. No subscription.

  • All modes, from Lite to Super
  • Run sessions in parallel
  • Monthly budgets and per-session caps
Get started

Team

Custom

Volume pricing for teams that hand off work every day.

  • Everything in Pay as you go
  • SSO, enforced MFA and SCIM
  • Audit log with CSV export
  • Shared Knowledge and playbooks
Talk to sales

Enterprise

Custom

For teams that need it in their own environment.

  • Runs on your Cloudflare account or your own servers
  • Custom data retention
  • Volume DU pricing
Talk to sales

How Dev Units add up

DU = model cost × 1 markup ÷ $1.98 + running sandbox minutes × 0.05

$1 of model usage + 20 minutes of sandbox = 1.505 DU ($2.98).

Runs started through the Agents API carry a 1.3× model multiplier: the same example is 1.657 DU ($3.28).

A FEW THINGS WORTH KNOWING

Before you hand off the first task.

What happens after I describe a task?

SaaSWish works in a session with its own workspace. Follow its plan, inspect the shell and browser, and review file changes. With a connected GitHub repository, the agent can commit, push and open a pull request.

Can I steer the agent while it works?

Yes. Send a message at any time, stop the current command, or turn on step mode to approve each plan step before files change. Risky commands have their own approval flow.

Can I undo a workspace change?

SaaSWish saves checkpoints before steps that change files. Stop the agent, then restore a checkpoint from Changes. Restore saves the current state first, so you can undo it. Your commits, branches and staging area are not changed.

What survives when a sandbox sleeps?

Workspace files are kept for the next wake. Running processes do not survive sleep. On Cloudflare, if a snapshot expires, the workspace backup restores files without dependency folders, so dependencies may need installing again.

How does usage billing work?

Dev Unit credits cover thinking and machine time. Buy prepaid credit packs and set an organization monthly budget or a per-session cap. New turns pause when credits or limits are exhausted; spend alerts help you track the balance.

Can we connect our identity and internal tools?

Use OIDC single sign-on, require two-factor authentication for members, and provision users through SCIM 2.0. Connect MCP servers for more tools, or start sessions through the REST API.

LET’S FIND YOUR FIRST TASK

What’s waiting in your backlog?

Create an account and hand off your first task in a few minutes.

Get started