timbuk2 ai
Precision Marketing Plan, measure and prove out-of-home campaigns with verified audience truth. Field Execution Know where to deploy field teams — and prove what happened. Retail Media & Activation Turn retail and township demand into verified, brand-funded sales. Audience Intelligence On-demand, ground-verified location and audience data for any geography. View all solutions
What we do Traction Our story Blog Open source Book a demo

FOONA COMMONS · OPEN-SOURCE COMMITMENT

Open infrastructure for evidence from the places maps miss.

We are preparing the reusable field-to-signal layer behind FOONA for public release: low-bandwidth collection, evidence provenance, verification interfaces, and privacy-safe aggregate reporting.

See the release roadmap Visit our GitHub

WHY OPEN

Field evidence should travel farther than one vendor.

Organisations working in low-data environments repeatedly rebuild the same collection and verification plumbing. FOONA Commons is our plan to make that machinery reusable, inspectable, and deployable by others.

Timbuk2 will offer managed deployments, integrations, and data operations on top. The public-good layer remains useful without access to our private participant network, client systems, or proprietary datasets.

THE OPEN BOUNDARY

Reusable by design. Protective by default.

WE PLAN TO OPEN

The field-evidence machinery

  • Versioned mission and consent schemas
  • Low-bandwidth capture adapters and reference interfaces
  • Evidence provenance and verification APIs
  • Privacy-safe aggregate metrics specification
  • Reference deployment, tests, and implementation guides

WE WILL PROTECT

People, partners, and legitimate commercial IP

  • Personal data and precise participant submissions
  • Child-identifying or safeguarding-sensitive information
  • Client configurations, credentials, and contracts
  • Proprietary datasets and enterprise decision models
  • Security-sensitive anti-abuse thresholds and private operations

OUR RELEASE STANDARD

Open source is a system, not a ZIP file.

01

Runnable

A documented local reference deployment with synthetic example data.

02

Inspectable

Versioned schemas, tests, release notes, and a software bill of materials.

03

Contributable

Clear contribution, governance, security, and maintainer policies.

04

Accountable

Published metric definitions and aggregate progress without exposing people.

RELEASE ROADMAP

A staged path to a credible public commons.

  1. NOW

    Scope and safeguard

    Separate reusable code from personal data and commercial systems; complete IP, dependency, secret, and child-safeguarding reviews.

  2. RELEASE 0.1

    Publish the foundation

    Release schemas, interfaces, synthetic fixtures, local setup, tests, licences, contribution guidance, and a security policy.

  3. REFERENCE PILOT

    Prove independent reuse

    Deploy with an implementation partner and publish aggregate, privacy-reviewed indicators against documented definitions.

  4. STEWARDSHIP

    Maintain in public

    Use an open issue tracker, versioned roadmap, changelog, and transparent release cadence to make outside contribution practical.

PRIVACY & SAFEGUARDING

Public progress must never mean public people.

Public reporting will use aggregate indicators, minimum-cell rules, and location generalisation. Personal records, raw media, precise child-linked locations, and partner-restricted data will not be published.

Until the first licensed release is published, this page is a commitment and roadmap — not a claim that FOONA Commons is already open source.

BUILD WITH US

Bring a field-evidence use case.

We want early implementation partners who care about low-bandwidth access, interoperable evidence, and responsible public data.

Start a conversation