Building blocks
When you build a house, nobody makes the windows and doors themselves. They come ready from the factory and get fitted. Your site works the same way: login, sign-up list or a system for content already exist, tested and measured. You choose, your AI fits them.
The one question
Should people sign up, log in or enter something on your site? Or do others look after the content in the browser?
No: a normal site
Light is enough, even in several languages. No building block needed:
- Text and pictures, one folder per language
- Lists like dates or products as a file in the project
- Payments with a payment link, for example from Stripe
- Newsletter through a service like Brevo
Yes: a site with building blocks
Building blocks run on your own server, so you need Pilot. Your logbook and address come with you when you switch.
PilotThe building blocks
Sign-up list
People sign up, you see the list. For courses, events and waiting lists.
PilotMemory while running: about 20 MBPocketBaseTell your AI:
Fit the sign-up list building block for me.Members’ area with login
Members register, log in and see an area of their own.
PilotMemory while running: about 20 MBPocketBaseTell your AI:
Fit the members’ area with login building block for me.Noticeboard
Others post news or dates in the browser, without a terminal.
PilotMemory while running: about 20 MBPocketBaseTell your AI:
Fit the noticeboard building block for me.Big CMS
Many kinds of content, several roles, image management and later an app too.
PilotMemory while running: about 200 MB, up to 2.5 GB while buildingStrapi + PostgresTell your AI:
Fit the big CMS building block for me.
Will it fit on my server?
A server with Pilot has 4 GB of memory. Website, PocketBase and Strapi together use about 250 MB while running. Sign-up list, login and noticeboard share a single PocketBase. Measured on 28 October 2026.