TopK
Technology Stack
Modern web stack
As of September 24, 2026, TopK's stack: The live site shows AWS as infrastructure alongside Cloudflare, Datadog, and Next.js, plus five additional detected technologies. AWS as the infrastructure layer is consistent with the private networking control and relevant for buyers with AWS-centric procurement.
Backed by 10 dated facts
Every value derives from a dated, sourced capture — open any fact for its source.
Every value derives from a dated, sourced capture — open any fact for its source.
Detected on the live site · observed
AWSCloudflareDatadogNext.jsPostHogReactTailwind CSSVercelYoutube
Infrastructure · observed
Vercel
Subdomain surface · 3 crawled
docs.topk.iocrawled · observed
Next.jsReactTailwind CSSVercelPostHogVercel · hosting
status.topk.iocrawled · observed
Next.jsReactTailwind CSSVercel
www.topk.iocrawled · observed
Next.jsReactTailwind CSSVercel
Stack Change Historydated events · values unlock with a key
Technology removed: VWO · high significance
Every stack fact on this pagekey · value · provenance · dated · sourced
| Fact | Value | Provenance | As of | Source |
|---|---|---|---|---|
| stack.infra.hosting.vercel | Vercel | observed | 2026-07-02 | docs.topk.io |
| stack.tech.aws | AWS | observed | 2026-09-24 | trust.topk.io |
| stack.tech.cloudflare | Cloudflare | observed | 2026-09-24 | trust.topk.io |
| stack.tech.datadog | Datadog | observed | 2026-09-24 | trust.topk.io |
| stack.tech.nextjs | Next.js | observed | 2026-09-24 | www.topk.io |
| stack.tech.posthog | PostHog | observed | 2026-09-24 | docs.topk.io |
| stack.tech.react | React | observed | 2026-09-24 | docs.topk.io |
| stack.tech.tailwindcss | Tailwind CSS | observed | 2026-09-24 | www.topk.io |
| stack.tech.vercel | Vercel | observed | 2026-09-24 | www.topk.io |
| stack.tech.youtube | Youtube | observed | 2026-09-14 | docs.topk.io/architecture |
Stack across Vector DatabasesTopK ranked in place · tap through for each read
IdentityBixel ID · free forever
Operated by
No registered company joined yet. Would resolve with: a registry identifier for the entity; a legal page on the site naming the registered company.
Registry identifiers
None on record.
Published identifiers
- Crunchbase topk · inferred
- GitHub topk-io · inferred
- LinkedIn topkio · corroborated
- X topk_io · corroborated
Get stack for topk.io via API / MCPevery field dated and sourced
RESTopen tier
GET https://api.bixel.com/v1/companies/topk.io/facts?dimension=stack
{
"data": {
"facts": [
{
"key": "stack.infra.hosting.vercel",
"value": "Vercel",
"provenance": "observed",
"as_of": "2026-07-02",
"source_url": "docs.topk.io"
},
{
"key": "stack.tech.aws",
"value": true,
"provenance": "observed",
"as_of": "2026-09-24",
"source_url": "trust.topk.io"
},
{
"key": "stack.tech.cloudflare",
"value": true,
"provenance": "observed",
"as_of": "2026-09-24",
"source_url": "trust.topk.io"
},
{
"key": "stack.tech.datadog",
"value": true,
"provenance": "observed",
"as_of": "2026-09-24",
"source_url": "trust.topk.io"
},
"…"
]
}
}MCPfor agents
# any MCP client (Claude, agents)
const record = await bixel.get_company_facts({ domain: "topk.io", dimension: "stack" })
# returns the stack record above,
# each value with its source_url + as_of,
# ready to reason overBuild on the company record. One key, REST + MCP, every signal dated and sourced back to the page it came from.
Public record, read from companies' own pages and boards. Every fact dated and sourced; provenance (observed vs company stated) shown inline.