Skip to main content

Architecture

A plain-language look at how Repuvane is built and where your data actually lives — useful if you're evaluating the product for your business, not a full engineering reference.

The three pieces​

Authentication — Clerk Sign-up, sign-in, and account/session management are handled by Clerk, a dedicated identity provider. Repuvane never stores your password.

Data — Convex Your business profile, voice settings, reviews, drafts, decisions, and audit trail live in Convex, a real-time database. Every change — an approval, an edit, an escalation — is recorded as part of an append-only history, not just overwritten.

AI drafting — Anthropic's Claude When Repuvane drafts a reply, it calls Anthropic's Claude API with your voice settings (tone, example replies, do-not-say phrases, sign-off) as instructions, plus the review itself. The draft comes back, is shown to you, and nothing is sent anywhere else until you approve it.

What never happens automatically​

  • Repuvane never posts a reply to Google, Yelp, or Facebook without your explicit approval. There is no "auto-post" switch to accidentally leave on.
  • Repuvane never uses your reviews or replies to train a shared model across other businesses.
  • A review flagged as needing escalation is never auto-resolved — it stays in your queue until a person handles it.

Team access​

If you invite a teammate, Repuvane uses Clerk Organizations to manage that membership — see Team Roles for what an Owner vs. a Worker can do.

Where things run​

The application and its API run on Vercel. The database (Convex) and authentication (Clerk) are each independently-operated, industry-standard infrastructure providers — Repuvane doesn't run its own database servers.