The tools that earned their place

Nothing here is a shiny toy picked to look good on a CV. Every tool on this list earned its spot over years of real client projects, and it stuck around because it makes the result faster, more reliable, or cheaper. Here's the full map: what we use, why, and what it actually does for you.

56
technologies in daily use
7
directions under one roof
8+
years building for the web

Four rules a tool must clear to earn its place in the stack

  • Speed is not negotiable

    Static-first, with a performance budget on every project: the site loads in under a second, or the job isn't finished. A tool that slows things down never makes it into the stack.

  • Your code, your data

    No lock-in, ever. You get the repository, the documentation and the deploy pipeline, and wherever we can, we reach for open tools. You're free to walk away any time, no ransom involved.

  • Proven in production, ahead of any demo

    Only tools we've already proven on real projects make it to production. We test anything new on our own work first, before we ever trust it with yours.

  • The right tool for the job

    We don't chase hype. When something simple genuinely fits the job, we keep it simple, and save the heavy machinery for when it's actually needed.

Choose a direction and see what powers it

Seven directions, all running on one proven stack. Open any of them to see what's inside.

Web Development

Site speed gets decided in the stack you build with. Ours ships sites that load in under a second, from marketing pages to e-shops and full web apps.

Frontend

HTML5

The markup language every page is built on. Clean, semantic structure is step one for SEO and accessibility on every site we ship.

CSS3

The styling language of the web. We write layouts, animation and responsive behavior in plain CSS, no heavy framework dragging the site down.

TypeScript

JavaScript with a type system attached. It keeps our sites and apps maintainable for years, catching errors while we build them, before they ever reach production.

Astro

Our framework of choice for content sites. It ships static pages with almost no JavaScript, which is why our marketing sites load in under a second.

React

The library we reach for on interactive interfaces, any web app, dashboard or client portal where a lot happens on screen at once.

GSAP

The animation library behind the motion on this very site: smooth, jank-free movement, micro-interactions, scroll effects, transitions.

Backend & data

Node.js

JavaScript running on the server. It drives the custom APIs, booking systems and internal tools we build, one language across the entire project.

PostgreSQL

The relational database we trust with e-shop and application data: reliable, built to scale, and ready to grow with the project.

REST & GraphQL

The interfaces systems use to talk to each other. We connect sites to CRMs, warehouses, payment providers and any third party, cleanly, and documented.

E-commerce

Shopify

The e-commerce platform for a fast start to selling online. We build stores on it that need no custom backend, from themed setups to fully custom storefronts.

MedusaJS

Headless e-commerce built on Node.js, our pick once a shop outgrows template platforms: custom checkout flows, B2B price lists, deep integrations.

Stripe

Payment infrastructure we wire in for cards, subscriptions and marketplace payouts, secure and friction-free right at checkout.

Infrastructure & ops

Vercel

Hosting for modern sites, backed by a global CDN. Deploys take minutes, the site stays fast from anywhere, and there's no server to babysit.

Cloudflare

CDN, DNS and attack protection rolled into one. It keeps client sites fast and online even when traffic spikes.

Git & GitHub

Version control for every project. Each one lives in a repository with full history, so the client always knows what shipped, when, and why.

Services in this direction

The anatomy of a fast website

Most sites are slow because they rebuild the page on every single request. We build the other way around: finished HTML ships instantly, and the heavy parts only kick in where there's genuinely no way around them. Here are those same layers, from the bottom up.

  1. Content and templates

    Copy, structure and components all live in Astro and TypeScript, one single source every page gets assembled from.

    • Astro
    • TypeScript
    • Markdown

  2. Static HTML

    Pages get built ahead of time into clean HTML and CSS. The browser has nothing left to wait for, so the first screen shows up in under a second.

    • HTML5
    • CSS3
    • GSAP

  3. Dynamic on demand

    Search, accounts and checkout run on serverless functions. They spin up only when needed, scale themselves, and leave no server for anyone to babysit.

    • Node.js
    • Serverless

  4. Data

    PostgreSQL and clean APIs store and serve the data behind a shop or an app, reliable, predictable, and ready to grow with it.

    • PostgreSQL
    • REST & GraphQL
    • pgvector

  5. Delivery and ownership

    A CDN serves the site fast worldwide, and every line of code lives in your own Git repository with full history and auto-deploy. Nothing hidden in a black box.

    • Cloudflare
    • Vercel
    • Git & GitHub

What people usually ask about the stack

Why Astro and not WordPress?

Astro ships finished HTML with almost no JavaScript: the site loads in under a second, there's barely anything to break, and no weekly plugin updates to babysit. We know WordPress well too, and we'll suggest it when a project genuinely calls for it, say when the editor needs a familiar admin panel to live in.

Isn’t this vendor lock-in?

No. You get the repository, the documentation and a configured deploy. The stack is standard and open, so any competent developer can pick up the project after us. We earn the next one with results, never by locking you in.

Do you work with our existing stack?

Yes. If you already have a site or a system, we start by understanding what's already there, then tell you straight what's worth keeping and what needs redoing. Improving what exists is often faster and cheaper than starting from scratch.

Why do you use so little JavaScript?

Every kilobyte of script slows the site down and adds one more thing that can break. We load JavaScript only where it's genuinely needed, and serve the rest as static. Less code in the browser means faster, more stable, and safer.

How reliable and secure is this?

A static site gives an attacker almost nothing to work with: no admin panel or database sitting behind every page. We wrap the dynamic parts in a CDN, a WAF and error monitoring, and keep client sites watched so we hear about a problem before the user ever does.

Who owns the code and data after launch?

You do. The repository, the database, the domains and the accounts are all in your name and stay with you. What we leave behind is documentation and a proper handover, never a set of keys we hold onto.

Ready to build something solid?

Drop us a message. We reply within a few hours to set up a quick chat.

  1. 1Within hours: a human reply: first thoughts, maybe a question or two.
  2. 2Within days: a 30-minute call. You talk, we listen. Free, no obligations.
  3. 3After the call: a written fixed quote, or an honest answer that we're not the right fit, with a tip on who to ask instead.

No sales scripts. You'll be talking to the people who'll actually build it.

Allergic to forms? Fair.info@chronicles.cz+420 773 230 278

By submitting this form, you're agreeing that we can use the details above to answer your enquiry. How we handle your data. We use it only to reply. We never sell it or add you to a mailing list.