API Maker
The backend engine for the AI era
SSR websitesEpisode 48 6:15 12 chapters November 2026
API Maker serves websites too: pages written in TSX, rendered by the server right next to your data, edited and previewed in the panel. Make the first pages of the Calm Home shop from a template: files are routes, compiled at the save, and previewed live on every screen size.
In the playlists The complete course SSR websites
API Maker serves websites too. You write the pages in TSX. The server renders them right next to your data, and you edit and preview them in the panel. In the next few minutes, you make the first pages of the Calm Home shop.
Even a simple website usually needs a lot. A separate frontend project. Its own server, to run and patch. An API layer between the pages and the data, with CORS, and tokens in the browser. A build and a deploy pipeline. And a security review of every form. With API Maker, a website is a folder of TSX files in the panel. The server that already holds your data renders it.
It is compiled the moment you save. And it is secure by default: every value is escaped, every form is protected from CSRF, and the content security policy is strict. In this video: a website from a template, the workspace, files that are routes, a page edited with a live preview, a new page from a model, the site in a real browser tab, and how the server renders it.
SSR Websites is in APIs and Logic. The account has no website yet. So we make the first one. There are seven templates. Each one is a complete website, with comments that say why it is written that way. Starter shows every feature, and Blank starts empty. Then come Blog, Shop, Dashboard, Landing page, and Documentation. Shop lists what it shows: products with filters, a cart, sign in, checkout, and the orders of each customer.
The title is Calm Home, and the name is store. The name is part of the address: slash s s r, slash calmhome, the path of the account, then slash store. Make the website.
The workspace opens on the home page. At the top is the address of the website, and the problems of its files. There are none. On the left are the files of the template: pages, components, lib, data, public, and site dot config, the settings of the website. In the middle is the editor, with types for the pages. And on the right is the shop itself.
Files are routes. The Routes view lists them. index is the home page. products slash slug takes a part of the path. And a file under api is a JSON endpoint. It also says who can open each page, and which pages the server keeps in its cache. Preview opens one: the list of products.
Now let us change the home page. Its headline says: things for a calm home. Make it: Calm Home, made to last. Command S saves the file. The server compiles it at once, and the preview reloads by itself. There is no dev server, and no build step. A mistake shows up when you save, not in front of a customer. Remove a closing tag, and save. The file does not compile, the count of problems turns red, and the compiler says what is wrong, and where.
Undo, save, and the count is back to zero.
A new page starts from a model. New file from a template offers many: a page, a page with data, a form, a sign in page, a layout, a JSON endpoint, and an RSS feed. Pick Page, name it about, and make it. Write what Calm Home is, and save. The preview shows slash about. The preview can take the size of any screen. Pick a phone, turn it on its side, or type your own size.
The shop follows, because the template is responsive.
Settings says what the website can do, as site dot config says it: the tables it reads and writes, its sign in, and its content security policy. For its own domain, it even writes the nginx and Caddy blocks for your reverse proxy.
Now the real thing. The address opens the shop in a browser tab, and the new page with it. The browser gets finished HTML. It is one request, with no JSON to fetch, and no token in JavaScript.
How does it work? When you save, the compiler turns TSX into plain string templates, and reads the settings as values. Each version of the website is built once. Pages render in small JavaScript engines, on their own threads, in the same process as the database clients of API Maker. Every request passes the same gates: the address, the session, who can open the page, the CSRF check, and the cache.
A page reads its data on the server, in a loader. That is the next video.
Every website has the same folders. Its pages have types. And its settings are values that the server reads when you save, so a typo closes a page instead of opening it. This makes websites easy to review, for people and for AI assistants. The docs even have a guide written for assistants.
To sum up. A website comes from a template, at its own address. Files are routes. Pages are compiled when you save, and previewed live. New pages come from models. And pages render next to your data. Next: loaders, forms, and sign in. API Maker. Build faster, spend smarter, deliver better.
Length 7:45SSR websites
Length 7:13SSR websites
Length 5:34SSR storefront
Length 7:26Architecture