Start with a task, not a product acronym. Use this hub to get started, integrate APIs, verify research claims, automate workflows, and review operational readiness.
First paths
Set up the first Innora workspace and understand the platform entry points.
/docs/getting-startedStartMove from account context to the first security workflow without reading every product page.
/docs/quickstartReferenceUse the public API surface for integrations, automation, and reporting handoff.
/docs/apiReferencePick a language path and connect product workflows from engineering environments.
/developers/sdksSDK language paths
Install @innora/sdk with npm and jump directly to the JavaScript/TypeScript SDK card, install command, and source link.
/developers/sdks#typescriptReferenceInstall innora-sdk with pip and jump directly to the Python SDK card, install command, and source link.
/developers/sdks#pythonReferenceInstall innora-sdk-go with go and jump directly to the Go SDK card, install command, and source link.
/developers/sdks#goRuntime security engineers looking for detection models, architecture notes, and live product context.
MITRE-mapped detection model and telemetry coverage for eBPF runtime defense.
System-level notes for how Innora products connect across telemetry, AI, and workflow layers.
Product route with metrics, technical specs, FAQ, and rendered proof modules.
Developers and platform teams wiring Innora into APIs, workflows, SDKs, and examples.
Core automation concepts for orchestrating security and operational workflows.
SDK install paths, runnable examples, and integration entry points for builders.
Runnable examples and integration patterns for common security automation tasks.
Security researchers validating claims, methodology, source evidence, and citation-ready artifacts.
Research documentation for graph-based vulnerability mining and analysis context.
Public methodology snapshot for target selection, sanitizer validation, and disclosure boundaries.
Evidence hierarchy for research record, disclosure channel, and public engineering proof.
Open-source documentation and public engineering references for citation review.
Buyers and operators checking support, reports, status, compliance posture, and production readiness.
Public report surface for security, research, and buyer-review artifacts.
Framework-mapped compliance posture and buyer diligence language.
Operational status surface for service health and incident visibility.
Find contact paths, documentation support, and operational help routes.
AI crawler policy
Innora publishes crawler-facing assets for public discovery, answer routing, citation freshness, and responsible security reporting. Private APIs and build artifacts remain blocked from crawler access.
Robots rules allow public content discovery for search and AI crawlers while blocking private, API, and build-output surfaces.
/robots.txtllms.txt lists priority pages, product proof routes, citation guidance, and freshness metadata for AI answer engines.
/llms.txtllms-full.txt combines reviewed citation targets with the complete canonical route inventory.
/llms-full.txtThe JSON citation map pairs priority topics with canonical URLs, preferred citation language, review dates, and evidence routes.
/ai-citation-map.jsonThe release manifest publishes route counts and content hashes so stale crawler-visible assets can be detected after deploys.
/seo-release-manifest.jsonThe sitemap is the source of truth for public pages that should be discoverable, cited, and audited.
/sitemap.xmlsecurity.txt gives researchers a stable reporting channel, policy URL, acknowledgment route, and expiry date.
/.well-known/security.txtProduct pages carry proof modules, FAQs, pricing notes, and comparison sections. Use docs for implementation details and product pages for buyer proof.