Releases nobody can repeat
Every release is versioned and tagged, deployed the same way each time, and checked against a health endpoint before it counts as done.
ENG-04 · Cloud Infrastructure, DevOps & Database Engineering
Aqlaan runs the infrastructure behind its own platforms: containerized services next to their database, static sites served from Cloudflare's edge, and a release process that can roll back in one step.
The problem
Every release is versioned and tagged, deployed the same way each time, and checked against a health endpoint before it counts as done.
Sites with no server code are served as static files from Cloudflare's edge, close to visitors in Jordan and the region.
PostgreSQL schemas are designed per module and changed through migrations, so the data stays understandable as the platform grows.
Scope
Containerized production environments, PostgreSQL schema design, and edge CDN pipelines built for high availability and predictable cost.
Approach
Server-rendered stores and the API run as containers; company sites and admin consoles that need no server run on the edge.
TLS on every hop, security headers on every response, and database ports closed to the public internet.
Every release keeps the previous version ready, so going back is a single command.
Evidence
aqlaan.com and papayatrading.com are served from Cloudflare's edge, and the Dentrax and Toppik stores and the Aqlaan API run as containers.
Connect with our engineering and product team in Amman at info@aqlaan.com to discuss custom software development, HRMSTONE deployment, or e-commerce architecture.