Three products, live in production See the platform

AI products for bug capture, support and voice.

Sphoro builds three focused products for problems most teams currently handle with tools that were not designed for them. Each has its own API and its own console. All three run on the same infrastructure and the same security model.

Captures and transcripts redacted AES-256-GCM at rest Self-hosting available
sphoro · bugcatch live

Bug reports that arrive with the evidence.

One click records the screen, the browser console, the network calls and the environment. The model reads all four together and opens the ticket in the tracker your team already uses.

bugcatch.sphoro.com
BugCatchReport viewbugcatch.sphoro.com
The BugCatch report view showing a recorded session alongside the generated summary and reproduction steps.
Fits the stack you already run
  • Jira
  • Linear
  • GitHub
  • Slack
  • Webhooks
  • REST API
  • Postgres
  • Redis
  • Twilio
  • SIP trunks
  • Chrome extension
  • Web SDK
  • Node SDK
  • AWS
  • Self-hosted
3 Products in production Each on its own host, with its own API
10 weeks First commit to the third product July to September 2026
642ms Time to first word on a call The target is under 800 ms
4 kB The BugCatch web SDK Or the Chrome extension, with no code at all
Why Sphoro

Three problems most teams handle badly.

Not the ordinary path, which works. These are the few places where software meets the real world and the real world wins. They are expensive, they are difficult, and they are usually handled by a tool built for something else.

Sphoro's bet is that each one deserves a product. Three of them, sharing one set of infrastructure, so the second was cheaper to build than the first and the third was cheaper than the second.

See what we built for each

Reports that will not reproduce

BugCatch

A report arrives with no console, no network trace and no environment. An engineer spends an afternoon failing to reproduce it, and the ticket goes back marked cannot reproduce.

About a dayof engineering per bug that does not reproduce first time

Calls nobody picks up

Sphoro Voice

Every voice bot that has been hung up on shares one flaw, which is the pause. Wait longer than about eight hundred milliseconds and the caller knows they are talking to a machine, and stops trying.

800 msis where a caller stops treating it as a conversation

Tickets that needed one action

Customer Agent

A refund, a status lookup, a password reset. Work a person should never have seen, queued behind work only a person can do, with a chatbot in front of it that answers questions but cannot press the button.

Mostof a support queue is one API call inside a conversation
Products

Three products, sold and used separately.

Each product stands on its own, with its own site, API and price. Start with one, and add the others only if they earn a place in your stack.

BugCatch bugcatch.sphoro.com

Bug reports that arrive with the evidence.

One click records the screen, the browser console, the network calls and the environment. The model reads all four together, writes a summary and a likely cause, and opens the ticket in the tracker your team already uses.

Integration
Chrome extension, or a 4 kB web SDK
Captures
Screen, console, network, environment
Sends to
Jira, Linear, GitHub, Slack
Visit BugCatch
A BugCatch report showing the recorded session, the console and network activity, and the generated summary.
A report as the assigned engineer sees it.
Customer Agent New

A support agent that finishes the task.

The agent reads your documentation, your past tickets and live account state, then calls your own API to issue the refund, change the status or reset the account. When it cannot finish a request it hands a person the full thread and the account context. We also build agents for jobs outside support.

Integration
One embedded widget
Actions
Through your existing API
Escalation
Full transcript and context
Try the live demo
The Customer Agent console showing a resolved conversation next to the API calls the agent made.
A resolved conversation, and the calls behind it.
Sphoro Voice voice.sphoro.com

Phone calls answered in under a second.

Speech recognition, the model and speech synthesis stream into each other instead of running one after another, so the agent starts speaking before the earlier stages have finished. It stops as soon as the caller talks over it. You bring your own carrier and your own models.

Time to first word
642 ms
Carrier
Yours, over SIP or Twilio
SDK
@sphoro/voice on npm
Visit Sphoro Voice
The Sphoro Voice console during a live call, with the running transcript and per-stage timings.
A live call, with the transcript and stage timings.
Platform

What the three products share.

The products are separate. The infrastructure under them is not. That is why the third product took a fraction of the time the first one did, and why a security review of one covers the rest.

One integration each

A Chrome extension or 4 kB SDK for BugCatch, one phone number for Voice, one widget for the Agent. Most teams are running in an afternoon.

No personal data where it is not needed

Captures and transcripts are redacted before they are written to disk, and what is kept is bounded by the retention limit on your plan rather than held indefinitely.

Encryption and retention

AES-256-GCM at rest. Roles, audit logs and per-plan retention are enforced by the API rather than the console, so they hold for direct API users too.

Your existing tools

Jira, GitHub, Linear, Slack, webhooks and a REST API. Sphoro fits into the workflow you have instead of asking your team to move into a new one.

Shared model routing

All three products call models through the same router, which fails over to another provider mid-request if one stops responding. You can point it at your own models.

Runs in your account

Postgres, Redis and a Node API, deployable in your own cloud, with self-hosting available on Enterprise.

Demo

Try the Customer Agent.

This is a scripted preview that runs in your browser and sends nothing anywhere. It shows the call the agent makes before it answers, because completing the task is the part that matters.

  • Reads documentation, past tickets and live account state
  • Calls your own API to complete the request
  • Hands over to a person with the full thread attached
  • Built to your requirements for jobs outside support
Tell us what you need an agent to do
Sphoro Agent scripted preview
Ask me something a customer might ask, and I will show you how it gets resolved.
Use cases

Where the products are used.

These describe the kinds of business the products are built for. They are not named customer references. We can walk you through live systems on a call.

Digital lending

Applicants answered without a queue

Voice handles the verification call and answers when the applicant rings back about a document or a payment. The Customer Agent takes the ones that arrive in chat, calling your own API to move the application on.

WasA callback queue, and the application stalled behind it
NowAnswered on the first ring, or resolved in chat
B2B software

Bugs that reproduce first time

BugCatch sits in the product and in the support console, so a customer's report carries its own recording. The Customer Agent handles the tickets that were never bugs to begin with.

WasClosed as cannot reproduce, twice
NowA cause and three steps, already in the tracker
Contact centre

Calls answered on the first ring

Voice takes the call end to end and escalates to a telecaller with the transcript attached. The Customer Agent covers the same requests in chat, on the same infrastructure.

WasHold music, then a repeated explanation
NowAnswered in 642 ms, resolved or handed over
Traction

Three products in ten weeks.

Each of these runs on its own public host with its own API and console. The dates are the first commit in each repository.

JULY 2026
BugCatch Capture, replay and AI triage, with a browser extension and a web SDK.
AUGUST 2026
Sphoro Voice Sub-second telephony on your own carrier, with interruption handling.
AUGUST 2026
Retrieval and Customer Agent The shared knowledge service, and the agent built on top of it.

The shared work is already done

Model routing, the event bus, the identity model and the encryption were built once. A new product inherits all of it, which is why the third shipped in weeks rather than quarters.

One relationship, three budgets

A team can start with BugCatch in engineering and later add the Agent in support and Voice in the contact centre. Same contract, same security review.

Company

A small team building narrow tools.

Three products, and a deliberate refusal to build a platform before building the things that go on it.

Sphoro started from a straightforward view. Most software pain comes from a handful of moments that are genuinely difficult, and those moments deserve products rather than features attached to something else.

So we build them one at a time. BugCatch turns a vague report into a reproducible ticket. Sphoro Voice answers the phone inside a second. The Customer Agent resolves support requests end to end. Each one is integrated with a single API call, because that is the bar we would want as engineers.

AI where it decides somethingModels do the reasoning inside each product.
Privacy by constructionCaptures and transcripts are redacted before storage.
One API eachAny product integrates in an afternoon.
Built for productionEncrypted at rest, deployable in your account.
Founder
FAQ

Common questions.

What does Sphoro do?

We build three AI products: BugCatch for bug capture and triage, Sphoro Voice for phone calls, and the Customer Agent for support requests. We also build custom agents to order.

Do we have to take all three?

No. Each product has its own site, API and pricing. Most customers start with one.

How long does integration take?

Each product needs one integration: a Chrome extension or 4 kB SDK for BugCatch, one phone number for Voice, one widget for the Agent. Most teams are running the same day.

Can you build an agent for our workflow?

Yes. Tell us the job, whether that is sales, onboarding, operations or an internal tool, and we build an agent around your product, data and workflow.

Can we run it in our own cloud?

Yes. The stack is Postgres, Redis and a Node API, and it deploys into your account. Self-hosting is available on Enterprise.

How is data handled?

Captures and transcripts are redacted before storage, and everything at rest is encrypted with AES-256-GCM. Roles, audit logs and retention limits are enforced in the API.

Contact

Tell us what you are trying to fix.

Book 30 minutes with the team. We will tell you which product fits, or whether none of them do. If you are investing rather than buying, say so and we will bring the numbers instead of the demo.

Or email info@sphoro.com.