Brand and entity reference

The canonical name, description, logo, domains and social handles. Use these verbatim in directories, articles and structured data.

Why this page exists

Search engines and language models decide whether two mentions refer to the same organisation by comparing names, descriptions, domains and linked profiles. Inconsistency splits one entity into several weak ones. This page is the reference copy so every listing can match it exactly.

Canonical facts

FieldValue
Organisation nameCognitive Industries
Legal nameCognitive Industries
Short nameCognitive
Primary domaincognitive-industries.org
Canonical URLhttps://cognitive-industries.org/
Founded2024
LocationBrisbane, Queensland, Australia
General email[email protected]
Security email[email protected]
Privacy email[email protected]
Logohttps://cognitive-industries.org/assets/icon-512.png
X / Twitter@CogIndustry

Canonical description

Use this paragraph verbatim in directories, articles and structured data:

Cognitive Industries is an independent AI research and development lab in Brisbane, Queensland, Australia. We ship our own products, open-source our research, and build web platforms, AI systems, security tooling and computer vision for clients.

The one-line version:

Independent AI R&D lab in Queensland, Australia. Products, open source, research, and client software work.

Profiles (sameAs)

Logo files

Cognitive Industries icon

Do not recolour the mark, stretch it, or set it on a light background without the dark plate. Press kit →

Sources

Where this page states a standard, an obligation or a research result, this is what it is drawn from. All external, all checkable.

  1. Schema.org vocabulary — the structured-data vocabulary every page here uses
  2. Google Search Central: structured data — Google
  3. Core Web Vitals — Google — LCP, INP and CLS, the metrics analytics.js reports
  4. Open Graph protocol — the link-preview format
  5. WCAG 2.2 — W3C — the accessibility standard the pages are built against

Other documents

Crawler and bot policy

Which automated clients are allowed, which are challenged, which are blocked, and why the site does not use User-Agent as a security boundary.

API reference

The public HTTP API behind the site: endpoints, versioning, rate limits, authentication and error format. Machine-readable schema at /openapi.json.

Security practices

How this site and the systems behind it are secured: headers, transport, secrets, dependencies, monitoring and disclosure.

Last reviewed · Site changelog