Arqora Notes

Technical notes, decisions, experiments, and updates from Arqora.

A maintained record of how Arqora studies systems, makes technical decisions, documents experiments, and turns internal work into public software over time.

5 published notes

Ideas are cool. Shipping is better.

Arqora is officially transitioning from conceptual design to active production, laying down a central identity control plane and edge-routed project infrastructure.

Quick summary
01

Arqora is officially transitioning from conceptual design to active production.

02

arqora.be is engineered as the central Identity Provider (IdP) and unified developer console.

03

arqora.work introduces an edge-routed project identity layer, bypassing manual DNS operations through wildcard resolution and dynamic ingress.

How Arqora handles public contact routes

A note on separating public contact paths for general messages, security, legal, support, and partnerships.

Quick summary
01

Arqora separates public contact routes so different kinds of messages do not collapse into one inbox.

02

Clear addresses make security, legal, support, and partnership messages easier to triage.

03

The routing is simple today, but it leaves room for future ticketing and operational workflows.

Early SEO decisions for arqora.be

A technical note on the early indexing, canonical, sitemap, and crawlability decisions behind arqora.be.

Quick summary
01

The first SEO work focused on making arqora.be crawlable without exposing duplicate deployment URLs.

02

Canonical URLs, sitemap entries, robots rules, and metadata were treated as infrastructure, not decoration.

03

The goal was to make the site understandable to crawlers before adding more public pages.