Pollenix
Available now in private preview

Answers with reasons.

A field manual for explainable AI — every answer ships with its receipts.

Pollenix is a deployable platform with a small Core, five licensed satellites, and the Why Engine at the centre. Every answer comes with a trace, drivers, citations, and a confidence band.

Files never leave your cloud. We gain coverage — metadata, ACLs, sensitivity — not consumption. Deploys into your AWS or Azure tenant from the marketplace.

Available in AWS Marketplace · Azure Marketplace · SOC 2 in flight · HIPAA-ready Health module
II. The Why Engine

Every answer is a citation.

Trace, drivers, counterfactuals, confidence — surfaced for every interaction.

We instrument every step the model takes. Retrieval scores, SQL plans, tool calls, DLP decisions, cost, latency. Then we layer attribution so you can see which dimensions moved the answer, and counterfactuals so you know how stable the answer is.

trace · 0a8e21f3 · why_engine v1 ok · 1.84 s
→ user.ask   "why is APAC revenue down vs last quarter?"
  01  retrieval     matched 3 columns                  score 0.72
  02  llm_call      sql-gen · gpt-4o                $0.003 · 1.2 s
  03  sql           executed                         442 rows · 18 ms
  04  driver        Region=APAC                      −9.0 pp
  05  driver        Segment=Enterprise               −2.1 pp
  06  counterfact.  prior quarter                    +4.4 pp delta
  07  guard         dlp.passed · auth_ctx valid     ok
  08  citation      sf_opportunities × sf_accounts  442 / 442
← answer     drafted, cited, safe to send.
Confidence 0.82
retrieval 0.72 logprobs 0.81 stability 0.91

/ accessible at GET /api/v1/why/{interaction_id}

III. Coverage, not consumption

Files stay in your cloud.

We index folders, ACLs, sensitivity. Never the bytes.

Coverage is the inverse of ingestion. We list, we classify, we map who can read what — and we stop there. Content reaches the model only on demand, on-behalf-of the asking user, with an audit trail and a DLP gate. No background sync. No silent copies. No cache.

Your cloud · S3 / Azure Blob

Source of truth

  • 📄contract-2026.pdf· high
  • 📄q4-deal-pipeline.csv· med
  • 📁patient-charts/· PHI
  • 📄employees-hr.xlsx· high
  • ·… 12,442 more
BYTES NEVER LEAVE THIS BOUNDARY.
Pollenix Coverage

Metadata. Only.

paths
12,447 indexed
acl graph
2,108 principals
sensitivity
PII · PHI · financial · custom
vectors
filenames + folder summaries
content
on-demand only
ZERO PERSISTENT COPIES.
i. Isolated mode

Per-user prefix. Only the owner can list, only the owner asks. Useful for the "my desk" workspace.

ii. Shared mode

Role / team scoped. ACL-driven visibility. The same coverage view for everyone allowed to see it — never more.

IV. Satellites

A small Core. Six satellites.

Each module licensed independently. Toggle on, toggle off, deploy what you need.

Pollenix Core is always on — Why Engine, AuthContext, Connector Bus, Coverage, DLP, Personality. Everything else is a satellite that loads at startup based on your license. No bundled bloat. No "available in enterprise" fog. Just a SKU.

  • I. NL→SQL over your warehouse

    DB Engine

    Connect Postgres, MySQL, BigQuery, Snowflake, Databricks, or DuckDB and ask plain-English questions. sqlglot validates every SQL (SELECT-only, dangerous-statement reject), schema-embedded retrieval picks the right tables, EXPLAIN preflight blocks billion-row scans, scope predicates AND-injected for row-level isolation. AuthContext-gated MCP tool db.run_sql is the only path through — drivers never called directly. Postgres + MySQL + BigQuery + Snowflake first-class.

    pollenix.db learn →
  • II. Dashboards over DB Engine

    BI

    Per-tenant dashboards with four widget kinds (chart / kpi / table / markdown) and seven chart spec kinds (line / area / bar / stacked-bar / donut / scatter / kpi / table). react-grid-layout 12-col canvas — drag from header, resize from corner, charts re-render to fit. Workbench → BI sends any answer to a board in one click. Ask AI about this widget rewrites the SQL via natural language without leaving the canvas. Public dashboards via revocable share tokens. Built on the DB Engine read-only contract.

    pollenix.bi learn →
  • III. EMR + RCM · FHIR R4

    Health

    Pollenix MR — AI-native EMR + full Mod-RCM on FHIR R4. Clinical loop: ambient scribe with audio-span citations, Problem List with decay, Med Reconciliation, Lab Inbox abnormal-first, Care Plans with auto-flip. Revenue cycle: AI charge capture, predictive scrubber (CMS NCCI + tenant-historical risk), 835 ERA + 277CA/999 acks, AI appeal letters, payer-contract underpayment detection, patient OOP estimator, A/R ledger. Patient portal, telehealth, AI voice contact center. Every write under per-call AuthContext + Why trace.

    pollenix.health learn →
  • IV. AI-native practice mgmt

    Legal

    Pollenix Law — AI-native practice management for law firms. Matters / clients / docketing / time. Firm Vault with hybrid retrieval; Assistant with inline citations; AI Drafter with CourtListener verifier. Practice agents (M&A / Litigation / Tax). Workflows + custom chains + playbooks (NDA / DD / 50-state / negotiation). Templates with matter merge. Cross-vault analytics. Citators (Westlaw KeyCite + Lexis Shepard's). DMS connectors (iManage + NetDocs). Word + Outlook add-ins. Slack + Teams bots. Email-to-Vault gateway. Matter-team ACLs. Per-firm fine-tuning. Why trace on every answer.

    pollenix.legal learn →
  • V. Contracts & risk

    FinTech

    Clause-by-clause contract diff with semantic alignment, risk surfacing, and natural-language follow-ups over the diff.

    pollenix.fintech learn →
  • VI. Infra · security

    Ops

    SSL scans, infra shield, scheduled scans with credential trend dashboards. The least-glamorous module that you'll quietly love.

    pollenix.ops learn →
  • VI. Reserved

    Yours.

    Build a satellite for your domain on the Pollenix SDK. The Why Engine and AuthContext come for free. We co-list it on the marketplace.

    partners@pollenix.ai →
V. Tech moat

Six things that take years to build right.

What makes Pollenix defensible isn't a feature list — it's the architectural choices the rest of the platform stands on.

Each pillar below is load-bearing across every satellite. Health's audit story is the same audit story Legal's is. The DB Engine's read-only validator is the same validator BI widgets execute through. The AuthContext gating one tool gates them all. The PQC envelope encrypting one credential encrypts every credential.

  1. 01 ML-KEM-1024 + ML-DSA-65 hybrid

    Post-quantum encryption

    Every at-rest credential lands under a NIST-standardized hybrid envelope: X25519 + ML-KEM-1024 KEM (FIPS 203), HKDF-SHA3-512 KDF, AES-256-GCM AEAD. Audit-chain fingerprints sign with ML-DSA-65 (FIPS 204). Hybrid is failure-safe — if either KEM is later broken, the other still protects. Ahead of the CNSA 2.0 federal mandate (2030); harvest-now-decrypt-later threat already addressed.

    FIPS 203 · FIPS 204 · X25519 hybrid · HKDF-SHA3

  2. 02 Retrieval · model · cost · timing

    Why Engine on every AI output

    No call to an LLM ships without a Why trace — retrieval breakdown (which chunks, which sources, which classifications), model used (including fine-tune overrides), per-event latency and cost, fingerprint signatures. Every assistant message has a Why button. Pre-discovery defensibility for any audit.

    per-event trace · ML-DSA-signed · in-memory rolling window

  3. 03 ≤ 30s · single-use · MCP-gated

    AuthContext capability tokens

    Every tool call carries a vault-signed capability JWS authorizing exactly the operation in scope. Tokens expire in 30 seconds, consume on first use, and the audit log records the consumption. No service has standing chart access, no standing DB access, no standing key material. Replay-safe.

    JWS · capability grammar · nonce-protected

  4. 04 sqlglot · identity-before-dispatch · EXPLAIN preflight

    Validator-gated tools

    Every external action goes through a validator before the driver is touched. The NL→SQL planner's output passes sqlglot (SELECT-only, dangerous-statement reject, scope predicates AND-injected). The voice agent's dispatch nodes require identity verification at runtime — flow graphs can't draw around it. DB queries pass EXPLAIN preflight to block billion-row scans.

    sqlglot AST walk · runtime identity lock · cost ceiling

  5. 05 EXISTS subqueries, not app-layer filtering

    SQL-layer ACLs

    Matter-team isolation for the Legal Vault. Tenant scope predicates for the DB Engine. Both apply at the SQL layer of vector and keyword retrieval — EXISTS subqueries the planner can't omit. Even a model with a stale context can't surface a chunk the asking user isn't allowed to read.

    PostgreSQL · pgvector · tsvector · matter_team

  6. 06 Your cloud · your data · BAA on file

    Deployable, not SaaS

    Pollenix Core runs in your AWS, Azure, or on-prem Kubernetes — Helm chart, Bicep / CFT, container image. Files stay in your cloud; the only outbound traffic is the AI provider you configure. AWS and Azure Marketplace listings; private-link supported.

    Helm · Bicep · CFT · AWS + Azure marketplace · BAA

Quantum-safe NIST FIPS 203 + 204 finalized August 2024 · Federal posture CNSA 2.0 ready before the 2030 mandate · Compliance SOC 2 in flight · HIPAA-ready · BAA on request
VI. Posture

Safety as a load-bearing wall.

The Why Engine is the differentiator; the security model is the floor.

  1. 01 ≤ 5 min · single-use

    AuthContext

    Every tool call carries a vault-signed JWS that authorizes exactly the operation. No standing privilege. Replay-safe via Redis-backed nonces.

    RS256 · capability grammar · nonce-protected

  2. 02 Per-tenant DEK · health key isolated

    Vault-derived keys

    Sensitive columns are encrypted with per-tenant DEKs derived from a vault-loaded ROOT_DATA_KEY. Searchable equality via blind indexes — never decrypt to filter.

    AES-256-GCM · HKDF · versioned rotation

  3. 03 Presidio · spaCy · custom recognizers

    DLP that stops the leak

    Three modes per role: detect-and-warn, detect-and-mask, detect-and-block. Logs run through the same pipeline so PII never lands in your observability stack.

    PII · PHI · financial · custom

Audit chain HMAC-linked rows · tamper-evident · Compliance SOC 2 in flight · HIPAA-ready Health module · BAA on request · Vendor AWS SM · Azure KV · GCP SM · HashiCorp Vault
VIII. Get in touch

Tell us what you're trying to figure out.

We answer every legitimate inquiry within one business day.

Whether you're sizing up a marketplace deploy, weighing the Health satellite for a regulated workload, or just want to see the Why Engine run against your own questions — leave your work details and we'll reach out.


Security
security@pollenix.ai Responsible disclosure · PGP on request
Partners
partners@pollenix.ai Build a Pollenix satellite

By submitting, you agree to our Privacy Policy and Terms of Service. We don't sell, share, or stockpile lead lists.

Direct line

Encrypted in transit. Stored only as long as we need it to reply.