Skip to content
VELTEINStart a project

~/veltein/studio — websites, platforms, automation

Websites that refuse to look like templates.

One deliberate design direction per project, built on a tested component system, with real 3D where it earns its place and a launch checked in a real browser.

See the workStart a project
Practice
Websites · web apps · automation
Built with
UX-STING · Next.js · Astro · Go
Ships as
Static, accessible, measured

Selected work

Nine projects, each with a full case study on veltein.com.

  1. 01CityBookA Morocco-focused local discovery platform connecting business listings, city information, search and localized content.Web platformNext.js · Go · PostgreSQL(case study opens in a new tab)
  2. 02RankCortexSEO, AI-readability and website operations tooling with audits, monitoring and search integrations.Web platformGo · PostgreSQL · APIs(case study opens in a new tab)
  3. 03BindPagesA recipe-to-ebook production application with content ingestion, AI processing and cookbook PDF generation.Web platformNext.js · NestJS · Go · Queues(case study opens in a new tab)
  4. 04Bella SalonA beauty-business website with service discovery, galleries and booking routes, rebuilt from WordPress.WebsiteNext.js · UX-STING · Cloudflare(case study opens in a new tab)
  5. 05ViraluxA Windows application for content discovery, design templates and publishing automation, with an Astro product website.Desktop & automationWindows · JavaScript · Astro(case study opens in a new tab)
  6. 06Epic Trip IdeasA travel-content website with structured guides, itineraries, search and publishing workflows.WebsiteAstro · Search · Cloudflare(case study opens in a new tab)
  7. 07UX-STINGA React component and theme system with semantic tokens, reusable interfaces and public demos. This page is built with it.Developer toolReact · TypeScript · Design tokens(case study opens in a new tab)
  8. 08Scraper GatewayA Go scraping service with provider configuration, key rotation and a web administration interface.Developer toolGo · PostgreSQL · Docker(case study opens in a new tab)
  9. 09Telegram CleanerA Python desktop utility for reviewing and removing selected Telegram bots, groups and channels.Desktop & automationPython · Telethon(case study opens in a new tab)
9

published case studies

6

service lines, one studio

11+

years of accounting and business operations behind the work

The method

Every page goes through a real browser before launch. What fails goes back to the build, not to the client.

How a VELTEIN site gets builtFlowchart: a brief leads to a design direction, then the build, then browser QA; pages that fail QA go back to the build, and pages that pass go to launch.PASSFIX + RETESTBriefDesign directiontype · palette · layoutBuildUX-STING · staticBrowser QApasses?LaunchLEGENDfocal stepreturn pathdecisionHow a VELTEIN site gets builtFlowchart: a brief leads to a design direction, then the build, then browser QA; pages that fail QA go back to the build, and pages that pass go to launch.PASSRETESTBriefDesign directiontype · palette · layoutBuildUX-STING · staticBrowser QApasses?LaunchLEGENDfocal stepreturn pathdecision
Brief to launch, with the QA loop that keeps templates and regressions out.
  1. 01

    Brief

    Who the site is for, what it must do, and the search terms it has to keep or win.

  2. 02

    Design direction

    One deliberate direction (type, palette, composition, one signature element) instead of a re-skinned template.

  3. 03

    Build

    UX-STING components and tokens, static output, and 3D or motion only where it earns its weight.

  4. 04

    Browser QA

    Real renders at phone and desktop widths, accessibility and performance checks. Anything that fails goes back to Build.

  5. 05

    Launch

    Domain, redirects, analytics, Search Console and Bing, then monitoring after go-live.

What the studio builds

What runs a launched site

Static pages on Cloudflare's edge, small functions only where a form or API needs them, and media in R2.

What runs a launched VELTEIN siteLayer stack from the visitor's browser down through the Cloudflare edge, the static site, functions and storage; most requests are answered at the edge.REQUESTL1Visitor's browserHTML · inline CSS · lazy three.jsL2Cloudflare edgeCDN cache · redirects · security headersL3Static siteNext.js or Astro export on PagesL4FunctionsWorkers · forms · small APIsL5StorageR2 media · D1 databaseLEGENDfocal layer: most requests are answered hereWhat runs a launched VELTEIN siteLayer stack from the visitor's browser down through the Cloudflare edge, the static site, functions and storage; most requests are answered at the edge.REQUEST ↓L1Visitor's browserHTML · inline CSS · lazy three.jsL2Cloudflare edgeCDN cache · redirects · security headersL3Static siteNext.js or Astro export on PagesL4FunctionsWorkers · forms · small APIsL5StorageR2 media · D1 databaseLEGENDfocal layer: most requests end here
Five layers, top to bottom; the edge answers most requests.

Have a site that should look like no one else's?

Start a project on veltein.com