Skip to content
tarıtas

AGENT ▸ Hello. You reached me, not voicemail.

I answer the phone for a city of 230,000 people.

I am a production voice agent. taritas engineered me. A regional IT firm sold me under its own brand. I live in the city's cloud, I write everything down, and I have answered every call since the day I went live.

Book a partner conversation Watch me take a call
743 msCaller to answer
24/7No queue, no hold music
0Bytes outside my client's cloud
14 yrsThe firm behind me
One call, slowed down 40×

Watch me take a call. All 743 milliseconds of it.

A resident calls City Hall. This is what I do with the call, step by step, shown the way my audit log would record it.

Live · municipal line 09:41 AM

CALLER ▸ When is bulk pickup on Maple Street this month?

AGENT ▸ You are in Zone 4: this Thursday, June 18. I set a text reminder for Wednesday evening.

✓ ANSWERED · WRITTEN TO THE AUDIT LOG

148ms ELAPSED BUDGET 800ms
01 · LISTEN · 148ms

I listen for the end of a thought, not the end of a sound.

Streaming speech to text with semantic turn detection. Callers pause, restart, and talk over me; I wait for the thought to land before I move.

Incoming audio → transcript caller ▸ "When is bulk pickup on Maple Street this month?"
02 · UNDERSTAND · 287ms

I read only what the city gave me.

My knowledge base is the city's own documents, embedded and pinned inside its cloud. The open internet is not in my vocabulary, so I cannot invent a pickup day.

Knowledge base lookup match ▸ sanitation/zones/zone-4.md
fact ▸ Maple St · Zone 4 · Thursday, June 18
03 · ACT · 190ms

The caller wants a reminder. I set one, for real.

Real systems, real writes. I act through the city's own APIs, and every write lands in the audit log next to the call that caused it.

Action · city reminder service POST /v1/reminders { when: jun-17 19:00, to: •••• ••82 }
✓ 201 created
04 · SPEAK · 118ms

I answer in a voice you can interrupt.

118 milliseconds to first word. Cut me off mid-sentence and I stop and listen; that is what makes me a conversation instead of a phone tree.

Spoken reply agent ▸ "You are in Zone 4: this Thursday, June 18. I set a text reminder for Wednesday evening."
05 · ON THE RECORD · after the call

I leave a paper trail on purpose.

Audio, transcript, and embeddings never left the city's cloud. This entry is what your client's security review reads. It is why I pass.

Audit log entry call 2026-06-12T09:41:07Z · 00:00:31
region pinned · in-country · retention 90d, enforced
actions 1 write · reminders.create
✓ nothing left the boundary

Representative call · timings from production · no real caller data appears on this page

Residency

I live in your client's cloud. I do not leave.

YOUR CLIENT'S CLOUD · THEIR REGION
  • my audio
  • my transcripts
  • my embeddings
  • my models
  • my audit log
CROSSES THE LINE: NOTHING
  • ✓My region is pinned at deployment and documented.
  • ✓My retention schedule is enforced in code, not in a policy deck.
  • ✓Every component I touch is on a subprocessor map.
  • ✓If taritas disappeared tomorrow, I would keep working. The client owns me.
The record

I am not the only one taritas runs in production.

Four sectors, every day. Our partners own these relationships, so names stay off the page. References under NDA.

Security

Five questions decide every deal. I carry the answers.

Most voice AI dies in procurement, not production. taritas hands your client this pack before contract, not after the audit finds a gap.

Where does the audio live?
✓In your client's cloud and region, pinned and documented.
How long is anything kept?
✓A written retention schedule, enforced in code.
Can we see what the agent did?
✓Every call and every action, logged and queryable.
Who else touches the data?
✓A subprocessor map covering every component and data path.
What if taritas disappears?
✓The client owns the IP and the accounts it runs in. The documentation is written for a team that has never met us.
Pricing

What I cost is public.

No “contact us for pricing.” The numbers are published, so you know them before we have even met. What you charge your clients stays your business.

from $2,000 Starter agent, owned outright
from $25,000 Custom build, their cloud
from $2,000 /moOperations, SLA-backed

The full sheet, including the partner margin model, is on the partner page.

The partner model

Your brand goes on me.

Your clients are already asking for voice AI. Saying "we don't do that" sends them somewhere that does. taritas is the engineering team that lets you say yes, and then stays invisible.

What taritas does for partners
  • ✓You sell, taritas builds. The work ships under your brand.
  • ✓IP transfers to you or your client, standard work for hire.
  • ✓We never contact your clients directly.
  • ✓No partner fees, no exclusivity, no minimums.

Buying for yourself, not reselling? Same engineering, direct. Scope a build.

AGENT ▸ I take live calls in the demo. Bring a hard question.

Thirty minutes. A live deployment. A straight answer.

taritas will show you a production system, walk the architecture, and tell you honestly whether a platform build is all you need.

Book a partner conversation

Reply within one business day