From stack trace to pull request.

Paste the error or connect the repository. You get the cause in plain words, the fix with a test, and a pull request to merge.

orders-service · pull request #42
  Batch the price lookups at checkout
  Branch     doko/batch-price-lookups
  Changed    2 files, 1 test
  Ready for you to merge

The cause in plain words, with the fix.

Attach the files or connect the repository. The reply names the line at fault and why it breaks, and the fix touches only what has to change.

You

Checkout times out when traffic spikes. Logs attached.

The timeout comes from one query per cart line in totals.js1. A forty-line cart makes forty round trips2. One batched lookup3 removes the wait, and a new test fails if it returns4.

2 files changed, 1 test addedcause and fix in one reply

Backends in the language you use.

APIs, databases, sign-in, payments, background jobs, uploads and realtime, for a new project or the one you already run.

Backend work

Ask for one piece, or a whole backend.

  • APIs
  • Databases and migrations
  • Sign-in and access
  • Security
  • Tests
  • Jobs and email
  • Payments
  • File uploads
  • Realtime
  • Performance
  • Running in production
Node.js, Python, Go, Java, PHP and Ruby

Every change arrives as a pull request.

Doko works on a branch of its own and asks before it opens the pull request. Your main branch changes only when you merge.

GitHub · orders-service
  Branch     doko/batch-price-lookups   ✓
  Changed    2 files, 1 test            ✓
  Open the pull request?
  [ Allow ]   [ Don't allow ]

Deployed to your own server.

Any Linux server you reach over SSH, from your own GitHub Actions. The server’s address and key stay in your repository’s secrets and never reach Doko.

Deploy · orders-service
  Server     your Linux server, over SSH
  Runs on    your GitHub Actions
  Keys       your repository’s secrets
  Deploy to your server?
  [ Allow ]   [ Don't allow ]

Questions, answered.

Anything else, ask support.

Which languages does Doko work in?

Most languages and frameworks. For backends: Node.js, Python, Go, Java, PHP and Ruby.

Does Doko push to my main branch?

No. It works on a branch of its own and opens a pull request. A merge into your main branch always asks first.

What can the GitHub plugin see?

Only the repositories you choose when you install it. You can change or remove that access on GitHub at any time.

Where do tests and app builds run?

On GitHub Actions in your own repository, with no limit from Doko. Public repositories run free; private ones use your account’s included minutes.

Can Doko deploy to my own server?

Yes, to any Linux server you reach over SSH. Doko deploys through your GitHub Actions after you allow it.

Can Doko call my live API?

Yes, on sites deployed to your own Vercel account. Reads run at once; a request that could change data asks first.

Bring the bug you’ve been putting off.

Paste the error, attach the files, and see what Doko finds. No card needed.