About us

Helping people keep what they know

InfoNest is a knowledge management platform built for anyone who captures more information than any single app can hold — from independent researchers to growing teams.

Concentric circles narrowing to a single point, representing focus and direction
Mission & vision

What we're building toward

We believe information is only useful if you can find it again. InfoNest exists to turn scattered notes, files, and links into a structured, searchable knowledge base that grows with you instead of against you.

Our long-term goal is simple to state and hard to build: a place where capturing an idea takes seconds, and finding it again — a year later, from a half-remembered phrase — takes just as little time. Everything on our product roadmap is judged against that standard.

Photo
Our story

How InfoNest got started

InfoNest began as an internal tool, built because our own team kept losing track of research across a dozen note-taking apps, shared drives, and browser bookmarks. What started as a weekend project to auto-tag a folder of notes became the search and structuring engine at the center of the product today.

We spent the first two years building for a small group of early users before opening the platform more broadly, refining the tagging and search behavior against real, messy, years-old note collections rather than clean demo data.

Three connected rounded tiles of varying height, representing shared principles
What we value

The principles behind every decision

These are the standards we hold the product — and ourselves — to when we're deciding what to build next or how to handle a difficult edge case.

  • Structure should be invisible

    Organization that requires effort doesn't get done. We build automatic structuring first and manual controls second, never the other way around.

  • Your notes are yours

    We treat personal libraries as private by default and design every sharing feature around explicit, revocable consent rather than implicit visibility.

  • Search has to be trustworthy

    A search tool that occasionally misses the right note is worse than no search tool, because it teaches people to stop trusting it. We test against real, messy libraries, not clean demos.

  • Slow and correct beats fast and fragile

    We would rather ship a feature a quarter later than migrate anyone's knowledge base through a lossy or irreversible change.

Photo
Process

How our team actually works

We're a small, deliberately cross-functional team: the people who design the tagging model also read support tickets, and the people who write documentation also sit in on customer calls. That keeps the gap between "how it's supposed to work" and "how people actually use it" as small as possible.

  • Ship in small, reversible steps

    Changes to search or structuring logic roll out gradually, with a clear way to fall back if something behaves unexpectedly on real libraries.

  • Read support tickets weekly, as a team

    Every team member, including engineers, reviews a sample of real support conversations each week to stay close to what's actually confusing people.

A staircase of ascending bars connected by a dotted line, representing progress over time
Milestones

How far we've come

A few of the moments that shaped the product into what it is today.

  • 2021 — First internal prototype

    A single-file auto-tagging script grew into a working search index for our own team's research notes.

  • 2022 — Early access opens

    A small group of independent researchers and writers began using InfoNest daily, shaping the first version of cross-linking.

  • 2023 — Team spaces launch

    Shared workspaces with role-based permissions made InfoNest usable for small teams, not just individuals.

  • 2025 — Graph view and offline access

    A visual map of linked notes and a fully offline-capable library brought InfoNest to its current shape.

A shield with a checkmark, representing security and trust
Trust & security

Why teams trust us with their information

Notes, files, and research often contain sensitive or unfinished work. We treat the responsibility of holding that information seriously, from how it's encrypted to who inside our own company can ever access it.

  • Encrypted in transit and at rest

    Your library is encrypted end to end while syncing and while stored, using industry-standard encryption on every device and server it touches.

  • Access is logged and limited

    Internal access to customer data is restricted to a small support team and logged, so any access can be reviewed after the fact.

A connected grid of nodes, representing structured, interlinked information
Who we serve

Built for how people actually work

InfoNest is used by people with very different relationships to information — but all of them need it to stay organized without extra effort.

  • Independent researchers and writers

    People assembling long-term reference libraries who need search to surface a note from months ago as reliably as one from this morning.

  • Small and growing teams

    Groups that have outgrown a shared drive and need one searchable source of truth without adopting a heavyweight internal wiki.