Integrations

Six inboxes.
One feed.

Krewva plugs into the messaging surfaces you already live in — natively, with the narrowest scope each platform allows. OAuth where it exists. Apple Full Disk Access for iMessage. Linked-client browser sessions for WhatsApp. Nothing screen-scraped, nothing piped through a shadow MITM.

Live today

All six are shipped, in production, used daily by beta accounts.

  1. Gmail Live Inbox copilot for personal + work mail.

    How it connects: Google OAuth — gmail.modify (read + send + label).

    • Reads Threads, labels, OOO state, and the messages your contacts send you.
    • Writes Drafts, sent replies you approved, and label changes on your behalf.
    • Stays local Nothing about Gmail is stored on the device — fetched per-card from Google.

    Highlights

    • OAuth scopes: gmail.modify (combined read + modify + send)
    • Reads 250+ messages on initial sync — ~8s ingest median
    • Auto-rules: route, archive, label, or auto-reply matching senders
    • Multi-account: Free 1 / Pro 3 / Business unlimited
    • Primary-inbox filter on by default — Promotions / Social / Updates dropped
    • Pub/Sub watch refreshed every ~6 days; OOO probe runs 6h cadence
  2. Slack Live Channels and DMs you actually need to read.

    How it connects: Slack OAuth — channels:history, im:history, chat:write, users:read.

    • Reads DMs, channels you joined, threaded replies, and user profile metadata.
    • Writes Approved replies, scheduled messages, and emoji reactions when relevant.
    • Stays local Workspace tokens stay encrypted in our vault — never on your laptop.

    Highlights

    • OAuth user token (not bot token) — Krewva reads as you, never as a bot
    • DM + channel + thread context fetched per draft
    • Workspace-scoped voice samples — your tone in #eng differs from a DM
    • Reactions: emoji-as-reply when a full sentence isn't warranted
    • Self-DND respected — drafts hold until you're back
    • We never join workspaces you weren't already in
  3. iMessage Live (macOS) Local-first. Your Mac, your messages, your control.

    How it connects: Full Disk Access grant — chat.db read, AppleScript send.

    • Reads Your local Messages.app database, the same way Spotlight indexes it.
    • Writes Replies via the Messages app — your Mac sends, not our server.
    • Stays local EVERYTHING. iMessage data never leaves your Mac in plaintext.

    Highlights

    • macOS only — runs as a sandboxed mac-agent companion to Krewva
    • chat.db rotation guard: re-bootstraps cursor on filesystem rotation
    • Cold-start backfill capped at 30 days — protects against poll storm
    • SMS fallback: opt-in per contact, never a default
    • AppleScript send via Messages.app — same channel as a human typing
    • If our backend is down, your incoming iMessages still flow
  4. WhatsApp Live Linked client via WhatsApp Web. No QR scan.

    How it connects: 8-digit phone-pairing code — same flow as the WA Web browser tab.

    • Reads Conversations on your linked phone, refreshed via supervised browser.
    • Writes Approved replies dispatched as a linked client (just like WA Web).
    • Stays local Pairing session token — never copied off the supervised browser profile.

    Highlights

    • Pairing flow: enter your phone number, type the 8-digit code on your phone
    • Supervised Playwright browser — stealth-plugin'd, never headless in prod
    • Deep-scan opt-in: when a chat shows >1 unread, navigate in to fetch full
    • Persistent browser context — login state survives reboots
    • Per-sender 60-min coalesce on inbound — one card per friend per hour
    • Selectors hot-reloadable via config/selectors.json — robust to WA rewrites
  5. Google Calendar Live Conflict-aware drafts + meeting briefs.

    How it connects: Google OAuth — calendar.readonly + calendar.events + freebusy.

    • Reads Your events, attendee lists, free/busy windows, and incoming invites.
    • Writes Event responses, declines with alternatives, and approved new events.
    • Stays local Free/busy is cached locally for 15 minutes — to dodge per-draft latency.

    Highlights

    • Pre-detect conflicts before drafting a yes/no
    • Two-stage decline: swipe-left enqueues a polite alternative-times draft
    • Pre-meeting brief: read the thread + Drive snippets 15 min before kickoff
    • Per-user dial: brief on every meeting, external-only, or off
    • Tz-aware fatigue cron — runs at your local 8am, not UTC
    • freebusy cache TTL = 15 min; cache outage never blocks card emission
  6. Google Drive Live Watched docs + comment ingest, scoped tight.

    How it connects: Google OAuth — drive.readonly only.

    • Reads Documents referenced in conversations + docs you explicitly watch.
    • Writes Nothing. We never modify or delete files in your Drive.
    • Stays local File contents are never persisted — fetched per-card and dropped.

    Highlights

    • OAuth scope: drive.readonly (no write, no delete, no permissions change)
    • Watched docs: poll for changes on docs you mark — not your whole Drive
    • Comment ingest: @-mentions surface as cards in your feed
    • Per-tier quota: Free 5 / Pro 50 / Business unlimited
    • Self-edit suppression: docs YOU just edited never re-emit a card
    • Daily digest: ≥3 daily notifications collapse into one 8am card

Universal access — works in any app

Krewva also lives in your keyboard. iOS keyboard extension + Android IME. Suggested responses you paste into any text box, in any app.

Krewva AI Keyboard

In development · Q3 2026

Tap the Krewva key in any app's text field. Get 2–3 reply variants in your voice. Paste. Send.

  • What it does Reads the visible context (the message you're replying to, if visible). Suggests 2–3 reply variants in your voice. Tap to insert into the active text field. Never reads passwords, 2FA codes, or payment fields — iOS sandboxes those.
  • Where it works Hinge / Bumble / Tinder / X / LinkedIn DMs / Discord / Snapchat / Telegram / WeChat / WhatsApp Business / Reddit / iOS Mail / Notes — and any app with a text box.
  • What stays private The Krewva keyboard NEVER uploads keystrokes. Your typing stays local. Only the invoked context (the message you're replying to) goes to the DeepSeek API for the 2–3 suggestions. No keylogging, no full-keyboard telemetry.

Coming soon

The four most-requested platforms from beta interviews. Drop us a line at hello@krewva.com to vote one up the list.

Ready to plug Krewva into your stack?

One signup, all six platforms. Disconnect any of them with one click — Krewva revokes access immediately and removes it from your active setup.

Closed-API apps like Hinge, Bumble, LinkedIn DMs? AI Keyboard handles those. Native integrations handle everything else.

See pricing & plans →