Data Outpost
San FranciscoNovember 4-5, 2026Applications opening soon

For builders at the forefront of AI + data

Two days on memory, agents, trust, interfaces, and data that can act.

Small-format. High-context. Built for frontier arguments.

// Field Notes

Data Outpost is the next evolution of Small Data SF: still human, still builder-led, but sharper and more future-facing for the moment when AI starts depending on the data systems underneath it.

The room is for founders, engineers, product leaders, researchers, operators, and designers making machine intelligence useful inside actual companies.

Small Data SF 2025 audience and stage moment
Small Data SF 2025 speaker moment
Small Data SF 2025 conference attendees

// Themes for Data Outpost 2026

THE NEXT AI BOTTLENECK ISN'T THE MODEL.

It's the data layer the model has to act through— and that's where the hard, unsolved problems still live. Memory, trust, agentic infrastructure, interfaces with taste. These are the four arguments that decide what AI-native data work becomes. We start them here.

01 / Systems

Agentic data infrastructure

02 / Product

Post-dashboard interfaces

03 / Trust

Memory, provenance, identity

04 / Craft

Tools with taste

// Where?

Date
November 4-5, 2026
Format
Talks, salons, demos, closed rooms

// Outpost scouts

Scouts at the frontier

Autonomous explorers mapping the unknown. They venture beyond the main body, gather signals, test boundaries, and report back.

Here are a few scouts you might encounter in the wild.

// Meet the scouts

Pathfinder scout with flag
Scout 01The Pathfinder

Charts new territory and marks what's next.

Observer scout with binoculars
Scout 02The Observer

Sees patterns others might miss.

Signaler scout with laptop and radio
Scout 03The Signaler

Collects signals and sends them home.

Cartographer scout with map
Scout 04The Cartographer

Maps systems, connections, and edges.

Builder scout with pack
Scout 05The Builder

Carries tools, builds what's needed.

// In the wild

// Outpost log 042

New territory confirmed.

More to map.

// Dispatch examples

Dispatch #01

Memory systems unstable.

Investigating long-term context retention.

Dispatch #02

Interfaces becoming operators.

Boundaries between UI and agent are blurred.

Dispatch #03

Trust embedded in infrastructure.

Verifying sources. Logging provenance.

// How they show up

Section openers and transitions

Callouts and side notes

Illustrations for themes and topics

Full agenda dropping soon.