Astryastry

Connect once. Capture forever.

Native connectors stream your tools into the brain and keep it current. Permissions inherit straight from the source — Astry maintains no parallel access store.

Sources.

Everything that feeds the vault: connectors, uploads, webhooks.

RefreshAdd source
Slack
Syncing

Channels, DMs, files. Add to Slack: OAuth, 1 click.

1,284 captures synced·Last activity 2 min ago
Configure
Google Drive
Connected

Sync files + folders. Connect with Google: OAuth.

3,902 captures synced·Last activity 14 min ago
Configure
SharePoint
Connected

Microsoft 365 sites. Connect via Entra admin-consent.

2,157 captures synced·Last activity 1 h ago
Configure
WhatsApp
Connected

Personal messages + media via paired device.

642 captures synced·Last activity 6 min ago
Configure
Meetings (Capvo)
Connected

Transcripts auto-ingested via webhook. Nothing to configure here.

318 captures synced·Last activity 32 min ago
Upload files

Drop files directly into the vault: backfills or one-off ingestion when no connector covers the source. Files run through the DLP input classifier first.

Drop files here or browse

Rights inherited from the source on every sync

One brain, every source.

Connect the tools your team already works in. Astry keeps them in sync and inherits their permissions, so nothing reaches a person who could not already see it.

Native connectors
SlackGoogle DriveSharePointMeetings

WhatsApp is in beta, and meetings flow in from your transcript webhook. Anything Astry does not connect natively reaches the brain through a REST ingest API, indexed under the same permissions and redaction rules as everything else.

Sync that respects the source.

Permissions inherit from the source

If a user cannot see a channel, they see nothing derived from it. Astry reads the source ACL instead of keeping a second copy.

Incremental sync

Each pass pulls only what changed, never a full re-ingest, so the brain keeps reflecting the latest state of every source.

Read-only by design

Connectors request read scopes only. Astry observes your tools, it never writes back to them.

Redacted at ingest

Deterministic rules detect secrets, cards and identifiers as content lands and rewrite them as placeholders before indexing, so the raw value never reaches the model.
How DLP works

Runs in your cloud

Connectors and their tokens live inside your own cloud. Astry holds no credentials to your environment.
See BYOC

Meetings, captured

Meeting transcripts and notes become searchable memory. Every decision is one question away.

From OAuth to current, in four steps.

No admin ticket queue, no parallel access list to maintain. Authorize once and the source stays in sync.

  • 01

    Authorize

    Sign in once through OAuth. Scopes are read-only and least-privilege, granted by your own admin.

  • 02

    Map permissions

    Astry reads the source ACLs and inherits them automatically. There is no parallel permission store to maintain.

  • 03

    Initial sync

    The first sync indexes existing content. Sensitive data is redacted as it lands, before the model can read it.

  • 04

    Stay current

    From there, sync is incremental. New messages, files and meeting transcripts flow in as they land, never a full re-ingest.

Good to know.

  • No. Connectors inherit the permissions of your source systems. If you cannot open a Slack channel or a Drive folder, nothing derived from it ever reaches you. There is no parallel permission store.

Bring your tools into the brain.

Slack, Drive, SharePoint, WhatsApp and meetings, plus a REST ingest API for everything else. Permissions come with them.