An engineering consultancy and general contracting office with work spread across design, technical office, permits, supervision and construction, and no single system holding any of it. Two brands and two domains to serve, in a market where the public face and the internal operation are judged together.

A full deployment of the GM-OS platform under their own brand: public website, staff portal, authentication, catalogue, billing, engagement, notifications, an orchestrator and an agent service, on a database of their own. The public site carries their identity throughout — their navy and gold, their logo, a language switcher and a dark mode — rather than ours with a logo swapped in.

The site is live on both domains with the client's own identity, their own navy and gold, a language switcher and a dark mode. The staff portal and central dashboard are live behind their own sign-in. Nine mailboxes are in use against an allocation of a hundred, so the mail side has room to grow into without another migration.

An integrated investment group needs a public face that can hold a portfolio — sectors, the companies inside them, the projects underneath those — and an internal system that does not stop at a brochure. Most of that structure is the first thing a template site flattens into a list of services.

A full platform deployment of their own: public website, staff portal, authentication, catalogue, billing, engagement, notifications, an orchestrator, an agent service and their own database — ten services in all. Six hosts were configured: the public site, www, an API host, a central dashboard, a mail host and the staff portal. Mail was brought onto our server under mam-group.ae with its own DKIM key, so their mail signs and authenticates as theirs rather than as ours.

The site is live with their own identity, structured around Sectors, Companies and Projects rather than a flat services list, with a media centre, careers and an English–Arabic switcher. The staff portal and central dashboard answer on their own subdomains behind their own sign-in, and nine mailboxes carry 229 messages against an allocation of a hundred and ten gigabytes — room to grow into without another migration.

A community organisation needing a public presence that could carry its programmes, schedule and volunteer paths, without the generic look that comes from building a charity site out of a template and a stock photo library.

A Next.js site of twenty-one statically generated pages covering programmes, schedule, gallery, getting involved, about and contact, with sitemap and robots handling. Every photograph, every line of copy and the video came from the organisation itself. Containerised and deployed alongside the rest of the estate.

The site is built, containerised and running healthily on the server. It is not yet reachable from the public internet: the domain has no DNS record pointing at it, which is the one remaining step and belongs to the organisation rather than to us.