Platform
Platform & architecture
How Tamanor works under the hood — and what it honestly does today.
- What is Tamanor?
Tamanor is a Social Account Firewall that monitors comments and reviews on connected social accounts, detects risk with AI, and prepares safe moderation actions a human approves.
- How Tamanor works
Tamanor connects via official OAuth, reads comments and reviews on a schedule and via webhooks, classifies risk with AI, and routes proposed actions through a human approval queue.
- Why Tamanor
Tamanor is built safe-by-default: official OAuth only, read-only by default, human approval before any action, row-level tenant isolation, and a full audit trail.
- Tamanor architecture
Tamanor is a multi-tenant application with a Next.js web app, a background worker, PostgreSQL with row-level security, and injectable platform connectors that isolate provider network calls from database transactions.
- Tamanor security
Tamanor connects only through official OAuth, never scrapes, never stores passwords, keeps tokens server-side and out of logs, and is read-only by default with human approval before any action.
- Row-level security (RLS)
Tamanor enforces tenant isolation at the database level with PostgreSQL row-level security, so a forgotten filter in application code can never leak another tenant's data.
- Audit log
Tamanor records every meaningful action — connections, syncs, proposals, approvals and moderation — in an append-only, tenant-scoped audit log that never contains token material.
- Permission model
Tamanor separates platform capability (what an account's OAuth grant truly allows) from workspace roles (what a team member is allowed to do), and offers an action only when both permit it.
- Role model
Tamanor uses role-based access within each workspace so owners, admins, analysts, reviewers and viewers see and do only what their role allows.
- Webhook architecture
Tamanor verifies every inbound webhook's signature, routes Facebook and Instagram events through one unified connector, rejects replays, and always resolves the tenant from the connected account — never from the payload.
- Worker architecture
A separate Tamanor worker runs scheduled read-only monitoring, token-expiry checks and webhook follow-up, each under a trusted tenant context and an account-level lease that prevents overlapping syncs.
- Data protection
Tamanor stores only the OAuth tokens and public content needed to protect a brand, isolates it per tenant with row-level security, keeps secrets out of logs, and cleans up short-lived onboarding data automatically.
- Privacy
Tamanor processes public social content and OAuth tokens for the sole purpose of protecting the connected brand, with tenant isolation, secret scrubbing and no selling of data.
- Encryption
Tamanor encrypts OAuth tokens at rest in production and blocks storing plaintext tokens in production, so credentials are protected even at the database layer.
- AI moderation
Tamanor's AI classifies each comment and review for risk and category, combining brand rules with AI analysis, then proposes actions for a human to approve — it never moderates automatically.
- Automation
Tamanor automates monitoring, risk detection and action preparation, but keeps execution human-approved: automation creates proposals, it never executes moderation on its own.
- Proposal engine
For high-risk items, Tamanor prepares a proposed moderation action with context and routes it to the approval queue; it proposes but never executes automatically.
- Roadmap
Facebook Page comment monitoring is verified live. Instagram is implementation-complete but verification-pending (Meta App Review). Google Business is a foundation pending approved API access. YouTube, LinkedIn and TikTok are research — not supported.