Skip to article body
A young engineer walking fast down an aisle of server racks, status lights stretched into long lines.
A young engineer walking fast down an aisle of server racks, status lights stretched into long lines.

Studio Notes · Announcements

Our Site, on Our Own Server

We rebuilt cairo-studio.com in SvelteKit and moved it onto a server we run ourselves. Here is why.

By Cairo Studio, Studio 5 min read

On 8 October we switched cairo-studio.com to a new version. It is rebuilt from scratch in SvelteKit, it replaces the old Next.js site, and it runs on a server we manage ourselves rather than on a hosting platform.

Why rebuild

The site is our portfolio, and it had fallen behind the work. Most of our recent client sites ship in SvelteKit, with heavy motion and Prismic behind them. Showing that work on a stack we no longer reach for first made less and less sense. The new site uses the same parts we build for clients: the same motion system, the same content model, the same bilingual setup.

Why our own server

We already run client apps and our own studio dashboard on servers we manage. Putting the site there too means one place to watch, one set of logs, and no surprise bill when a project page has a good week.

How it runs

  • Two copies of the site run side by side behind one web server.
  • A deploy restarts them one after the other, so one is always answering.
  • Content lives in Prismic, so publishing a project or an article needs no deploy at all.
  • The old site is kept stopped, not deleted, so going back takes a minute.

What changed for visitors

Faster pages, more of our work, and motion that matches what we actually build now. The Arabic version is built and waiting for a final review before it goes public.

We tell clients to own their stack. It was time we did the same.

More from the Journal

view all →