Built for the people who need to know first.
We think real intelligence should be available to anyone willing to use it, not only to organizations with a data team and a budget line for it. That conviction is in everything we build, including what we charge for it and who we'll sell it to.
Almost everything is built to explain the past.
Search returns what was crawled and ranked. Reports cover the quarter that finished. Analytics describe what already happened. All of it is useful and all of it is looking backwards, which is fine right up until the thing you need to know about is happening now.
We built the other half. Verdant reads the world as it publishes and answers questions about the present, and about whatever the world has already announced is coming. We are not interested in history. Plenty of tools cover that well.
Most of the worry comes from finding out late.
Almost nobody is anxious about the things they can see coming. They plan for those. What wears people down is the disruption that arrives without warning, the competitor move nobody caught, the supplier problem that surfaced a week too late to fix.
So the goal underneath all of this is quieter than it sounds. We want the people who use this to stop bracing. Knowing what is happening is what makes the difference between reacting and being ready, and being ready is a considerably calmer way to work.
- 01 Verdant Eye, for people and organizations
- 02 Intelligence Assistant, for developers and AI builders
- 03 Custom Intelligence Systems, built to order
- 04 Training, so you know what to ask it
- 05 Guardian Project, the same thing for everyone else
Guardian Project is the version for everybody else.
Everything else we sell goes to organizations that already know they need it and have a budget line for it. Guardian Project is the same platform pointed at anyone who simply wants to understand what is going on around them, asked in plain language, with no job title required to justify it.
It is being built now. It is also the reason we started this.
Network science, pointed at a practical problem.
Network science is the study of how things connect, how relationships form, and how information moves through a system. It is a real academic field, it is decades old, and it turns out to be exactly the right tool for this job.
Where most platforms retrieve documents, we map relationships. Where most answer from something cached, we answer from what is live. The difference shows up the moment a question has more than one moving part in it.
| Most platforms | What we do instead |
|---|---|
| Retrieve | They find documents that match your words. We map how things relate to each other, so the answer accounts for connections nobody thought to search for. |
| Cache | They answer from a stored copy, current whenever it was captured. We answer from what has published since, measured in minutes. |
| Isolate | They know your documents or they know the web. We put your internal knowledge and live world signals in the same place, so you can ask how one affects the other. |
We didn't just build this, we wrote the book on it.
This wasn't assembled over a weekend. It came out of years of original research, a very large number of hours of experimentation, and a stubborn interest in a problem most people had not noticed was solvable.
All of that happened in public, which matters more than the volume of it. Published articles anyone can read, a book you can buy, and a thousand or so researchers and practitioners following along and pushing back. You aren't taking a bet on a pitch deck.
A published book on the exact discipline this platform is built on, not a whitepaper we wrote about ourselves.
Go read itThe public record of how this was built, written openly the whole way through so anyone can pick it apart. Free, and always has been.
Go read itEvery capability we describe is deployed and working today. None of it is a mockup waiting on a roadmap.
See it liveThree people, and you'll meet all of them.
There is no sales team standing between you and the people who built this. Whoever you speak to first can answer the technical question you ask second.
David Knickerbocker
Wrote the book this platform's approach is built on, published the research in the open for years, has trained models and shipped production systems, and has started three companies. He runs the demos and teaches every course.
Michael Levin
Runs marketing, messaging and the front of the pipeline. If you got an email from us, he wrote the system that wrote it, and he'll be the one who replies.
Marc McLean
Runs outreach and every sales conversation from the first reply through to close. He's the one who will make sure the demo actually gets on your calendar.
Where we work
Based in the Portland metro area with active expansion into the San Francisco Bay Area, and we work with organizations well beyond both.
The parts that don't change.
Products move, pricing moves, and the website has changed more than once. These do not.
You know how we think. Come see what we built.
One conversation, no slides. Tell us what you're trying to understand and we'll show you what it does with it.
