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
Arqora is officially transitioning from conceptual design to active production.
arqora.be is engineered as the central Identity Provider (IdP) and unified developer console.
arqora.work introduces an edge-routed project identity layer, bypassing manual DNS operations through wildcard resolution and dynamic ingress.
We are out of the concept phase
Arqora is officially transitioning from conceptual design to active production.
We are no longer discussing future plans or mockups. We are provisioning the actual systems: identity planes, edge routing, deployment pipelines, verification layers, and the core infrastructure underneath them.
Architectural shifts will happen. Services will be refactored. But the objective remains singular: we are not just avoiding technical debt; we are building a foundation engineered to scale natively.
Layer 1: The Central Identity Control Plane
The base primitive of the Arqora ecosystem is arqora.be.
It is engineered as the central Identity Provider (IdP), OAuth 2.0 engine, and unified developer console. The architecture dictates one unfragmented identity across all Arqora products. A developer should never have to re-authenticate or provision separate credentials to access different nodes of the ecosystem.
Identity is the control plane. But the data plane—what comes after—is where the architecture gets interesting.
Layer 2: Edge-Routed Project Identity
The first workload running on this infrastructure is arqora.work—a discovery and identity platform for builders.
The traditional approach to a discovery platform is a static directory. Arqora takes a different architectural route: establishing a verified, addressable identity for the project itself at the network layer.
When a developer registers a project, they provide a source repository, a live origin URL (Vercel, AWS, Cloudflare, Custom VPS), and cryptographic or DNS-based proof of ownership.
Arqora runs automated security and verification heuristics. Upon validation, the system provisions a project record with a verified ingress route (e.g., https://nexus.arqora.work).
Crucially, Arqora abstracts the hosting layer. The developer retains full ownership and control over their underlying compute. Arqora acts as the verified ingress layer sitting in front of it.
Dynamic Ingress & Wildcard Resolution
Provisioning a dedicated DNS record for every new project does not scale efficiently. Instead, Arqora relies on wildcard DNS resolution mapped to our edge infrastructure.
Requests for nexus.arqora.work and atlas.arqora.work hit the same edge load balancers. The edge extracts the host header, queries the high-speed project registry, and dynamically proxies the request to the correct origin.
The DNS layer is completely unaware of the individual projects. The application edge handles the resolution.
The Request Lifecycle & Production-Grade Topology
When a client initiates a request, it terminates at the Arqora Edge. The edge parses the host header, queries the project registry, and securely proxies the request to the verified origin.
The client never needs to know if the underlying compute is an AWS Lambda, a Vercel deployment, or a bare-metal EC2 instance.
At scale, this requires a highly available, decoupled architecture. A conceptual topology mirrors standard enterprise cloud deployments using global CDN/Anycast, Application Load Balancers, and a multi-tiered Control Plane.
We are not locked into a single provider; the infrastructure primitives (DNS, Edge Compute, Load Balancing, Relational Databases) remain modular and replaceable.
Edge Security and Zero-Trust Proxying
Once Arqora controls the ingress traffic, the edge node does more than simple HTTP forwarding. It acts as a security and policy enforcement point.
This includes SSL/TLS termination, distributed rate limiting, Web Application Firewall (WAF) & abuse protection, origin health checks, and project-level access policies.
The subdomain is not a cosmetic URL. It is a programmable, addressable identity at the infrastructure layer.
Verification Before Ingress
Proxying arbitrary origins carries inherent security risks (e.g., SSRF, DNS rebinding, malformed traffic). Therefore, verification is a strict prerequisite.
A project achieves Verified status only after passing specific signal checks, such as DNS TXT record challenges.
Origins are treated as controlled configurations. They are never blindly trusted. Verification isn't just about proving ownership—it is fundamentally about making the infrastructure safer to operate.
The Bigger Picture
If arqora.work were merely a directory, we could have shipped a database, a search page, and called it done.
But we are engineering a system where projects possess a verified identity, an edge-proxied address, and a programmable infrastructure layer that understands the project behind that address. This requires identity engines, edge networking, dynamic DNS, and zero-trust security models.
We are building the foundation while the ecosystem is young, ensuring the architecture can absorb scale without requiring manual provisioning for every new project.
Idea → Prototype → System → Infrastructure → Products. Arqora is moving into the last four.
Ideas are cool. Shipping is better. And now, we are shipping.