Update
August 8, 2026
How we structure the site like Datadog
Every capability gets a URL. Solutions fan out. Learning compounds. The product stays narrow.
REDWOOD CITY, CALIFORNIA — Datadog’s marketing site wins on information architecture. Every capability has a URL. Solutions fan out by industry and technology. Learning content compounds. You can arrive from a search, land on the exact job you have, and still find the rest of the platform without getting lost in a homepage hero.
Vectornosis took that discipline and applied it to a company that does one warehouse job extremely well. We did not copy a catalog of thousands of pages for sport. We copied the idea that a serious product deserves a serious map.
On vectornosis.com that map is visible. VectorData capabilities live under /vectordata. Solutions split by use case, industry, team, and technology. Learn guides sit next to docs. Compare pages exist so a bake-off does not have to start from a blank slide. Integrations are real destinations, not a logo tray.
Narrow product, wide doors
VectorData monitors BigQuery and dbt. It reads metadata. It sends calm alerts. That sentence is the product. The site is wider because buyers do not search for “calm alerts.” They search for stale dashboards, broken models, warehouse cost, and whether a vendor will sample rows. Each of those searches deserves a page that tells the truth and points at the same command center.
Harbor and AmericaOS have their own homes. Labs — PlazaGPR, VectorChat, VectorSites — stay labeled as labs. The company is allowed to ship more than one thing. The flagship is still VectorData.
Every VectorData leaf should answer a job: what broke, how fresh, what it cost, what to fix first.
“Information architecture is a product decision. If a capability cannot earn a URL, it is not ready to be sold.”
Ricky Jiménez Sparks, CEO of Vectornosis
How a stranger should arrive
Someone searching “BigQuery freshness monitoring” should not have to decode a homepage metaphor. They should land on a leaf that names the job, shows the product, and offers the demo. Someone comparing vendors should find /compare without hunting through a blog index. Someone in security should find /security before they find a pricing argument. That is the point of the map.
We keep Labs labeled. PlazaGPR, VectorChat, and VectorSites are real, and they are not VectorData. Mixing them into the flagship pricing page would make the company look busier and the product harder to buy. The site is allowed to be a family. It is not allowed to be a blur.
What we refuse to page
We do not publish a capability we cannot open. We do not dress a waitlist as a workspace. We do not invent a logo wall to make the integrations page look finished. The Datadog lesson was structure, not sprawl. A URL with nothing behind it is worse than no URL.
That is why /resources exists as a hub, why this newsroom is a record instead of a dump of shipping notes, and why the command center is reachable before a sales call. If you cannot find the thing from the site, we have not finished the product — we have only finished the deck.
If you are evaluating Vectornosis, start at /resources. From there the map is honest: product, solutions, learn, compare, security, pricing, and this newsroom. The work is to keep those doors accurate as the software moves — not to decorate them.
