Memory and context for AI agents

Give your agents context they can explain.

The central nervous system for your organisation

Request a demo See how it works

Examples · illustration

One memory across every team.

Pollen links what each team knows. It reacts to changes, answers questions, and finds what did not happen.

Sources

#launch-atlasProduct

  1. Dana Reyes

    The Atlas launch is set for 18 May.

  2. Priya Shah

    Kestrel delivers the sensor boards on 12 May.

  3. Marco Diaz

    Assembly takes 5 days after the boards arrive.

Kestrel ComponentsSupply chain

Delivery update: SB-2 sensor boards

The sensor boards now ship on 14 May, two days later than planned.

Gmail · 06 May

Memory

PollenContext2 teams
  • Launch date18 May Dana
  • Sensor boards arrive12 May14 May PriyaKestrel 12 May is closed, not deleted. It stays on record.
  • Assembly time5 days Marco
Conflict found

14 May plus 5 days of assembly is 19 May. The launch is on 18 May.

Response

Decision

Notify the launch owner.

Owner notification · Dana Reyes

#launch-atlasThread reply

PollenAPP

@Dana Reyes Kestrel moved the sensor boards to 14 May. Assembly takes 5 days, so the 18 May launch is at risk.

Kestrel email · 06 May Marco · 03 Mar

Also sent to Dana Reyes by email.

  1. Step 1 of 5 · Team chatThe product team agrees the dates in Slack.
  2. Step 2 of 5 · MemoryPollen saves each message as facts with a source.
  3. Step 3 of 5 · Supplier emailSupply chain gets a new date. Pollen keeps the old one on record.
  4. Step 4 of 5 · ConflictPollen links the change to the launch and finds a conflict.
  5. Step 5 of 5 · ResponsePollen tells the launch owner in the thread and by email.

Sources

Acme renewal callSales

Sam Ortiz: “Acme renews if SSO ships by 1 June.”

Meet transcript · 28 Apr

ENG-412 · SAML SSOEngineering

In progress. The cycle ends on 6 Jun.

Linear issue

Security review: SSOSecurity

Tue 9 Jun, 14:00

Google Calendar

#salesSales

Sam Ortiz

Can we promise Acme SSO by 1 June?

Memory

PollenContext3 teams
  • Acme renewal needsSSO by 1 Jun Sam
  • SSO build ends6 Jun ENG-412
  • Security review9 Jun Calendar
Answer

No. The build ends on 6 Jun, and the security review is on 9 Jun.

Response

Decision

Answer Sam with the evidence.

Answer · Sales and the account owner

#salesThread reply

PollenAPP

@Sam Ortiz Not by 1 June. The SSO build ends on 6 Jun, and the security review is on 9 Jun.

ENG-412 Review · 9 Jun Call · 28 Apr

The renewal risk also goes to the account owner.

  1. Step 1 of 5 · SourcesSales, Engineering, and Security each keep their own records.
  2. Step 2 of 5 · MemoryPollen links the three records into one view.
  3. Step 3 of 5 · QuestionSales asks a question in Slack.
  4. Step 4 of 5 · AnswerPollen answers from the linked facts.
  5. Step 5 of 5 · ResponsePollen replies with the evidence and flags the renewal risk.

Sources

Brightwell kickoffClient services

Lena Park: “We will send the brand assets by Friday, 15 May.”

Meet transcript · 06 May

Campaign goes liveMedia

Mon 18 May, 08:00

Google Calendar

CRE-88 · Landing pagesCreative

Blocked. The pages need the brand assets.

Linear issue

Scheduled checkPollen

16 May: no email with the brand assets is on record.

Memory

PollenContext3 teams
  • Brand assets due15 May Lena
  • Campaign live18 May Calendar
  • Landing pages needBrand assets CRE-88
Missed commitment

The assets were due on 15 May. The pages need them before 18 May.

Response

Decision

Ask for an urgent review.

Urgent review · Omar Ali, account lead

#brightwellMessage

PollenAPP

@Omar Ali The Brightwell brand assets were due on 15 May and are not on record. The landing pages are blocked, and the campaign goes live on 18 May.

Kickoff · 06 May CRE-88 Live · 18 May

Also sent to Omar Ali by email.

  1. Step 1 of 5 · SourcesThe client promise, the launch date, and the work sit in three tools.
  2. Step 2 of 5 · MemoryPollen links the promise, the date, and the blocked work.
  3. Step 3 of 5 · CheckA scheduled check runs. The assets did not arrive.
  4. Step 4 of 5 · FindingPollen finds a missed commitment that blocks the launch.
  5. Step 5 of 5 · ResponsePollen asks the account lead for an urgent review.

How it works

Four steps from source to review.

A plan changes in a call. A contract keeps the old date. Pollen connects all three.

  1. 01

    Add sources.

    Send messages, emails, and documents as text. Pollen keeps each revision.

  2. 02

    Connect facts.

    Pollen links people, projects, and dates. A changed fact is closed, not overwritten.

  3. 03

    Answer with evidence.

    Each answer quotes its sources. If the sources do not support an answer, Pollen says so.

  4. 04

    Review changes.

    Pollen checks new information against what it affects. Findings go to the owner.

Monitoring

See what changed. Send it to the right person.

New information starts the work. No one has to ask a question first.

Scheduled checks find what did not happen.

Pollen reads due dates in your sources. After a due date, it checks for a confirmation. If none is on record, it records a finding.

You choose the response.

Pollen can notify the owner or ask for an urgent review. It delivers to an inbox or to your webhook.

Foundation

Built on Lattice, our own graph database.

Lattice keeps each fact with its source and its dates. Pollen uses it to connect, search, and remember.

Text fromMessagesEmailsDocuments

Pollen Context

Product

Memory

Sources, facts, and revisions.

Answers

Each answer quotes its sources.

Monitoring

Findings go to the owner.

Lattice

Graph database

Connected graphs

People, projects, decisions, and dates.

Search

Graph links, keywords, and vectors.

History

Event time and record time for each fact.

Separate graphs
One service holds many graphs. Each graph has its own log and snapshots.
Storage tiers
Idle graphs move to lower storage tiers. They load again on the next request.
Durable writes
Lattice writes each change to disk before it confirms the write.
Recovery
After a restart, each graph returns to its last confirmed state.

Build agents with a clearer view of your business.

Tell us what your agents do. We will show you Pollen Context.

Thank you. We will contact you by email.

Your request was not sent. Try again in a few minutes.