01
Template routes
Curated starts for founders, hospitality and culture-first brands that need speed without a borrowed look.
The world behind the flagship
Templates, demos
and system proof
for the wider
PixelPiraterij engine.
PixelPiraterij World is the tangible engine around the flagship studio. It is where template routes, live capability demos, product-facing proofs and rougher experiments become visible without pretending they all belong on the sales front.
The flagship closes the work. The world makes the wider system readable.
English-first by default, with Dutch still available as a real route.
Warmer materials, stricter structure, less AI-template fatigue.
01
Three routes, one harbor.
The move is not to flatten templates, apps and docs into one vague offer. The move is to make each lane tangible, then connect it back to the same operating model.
02
Apps and portals
Live utilities, focused tools and proof that the product side of PixelPiraterij is already operational.
03
Docs and lab
The notes, guides and experiments that keep the system honest while it expands.
02
Current starters, built from real directions.
This is the missing proof layer: not abstract template talk, but visible starting routes built from real PixelPiraterij directions that can later become editable products.
Template starterPixelPiraterij utility suiteBranded route panel
Template starter
PixelPiraterij utility suite
A compact starter route for utility-style products where pricing, unlock logic and a calm surface already need to feel sellable.
- Good base for small premium utility offers
- Shows how fast starts can still feel intentional
- Useful when the route begins with a focused paid product
Hospitality starterLe Radel booking routeBranded route panel
Hospitality starter
Le Radel booking route
A calmer hospitality direction that proves templates should start from audience behavior, not from a neutral skin with swapped colors.
- Nature-led hospitality framing
- Booking-aware page rhythm
- Softer trust language than a founder launch page
Cultural starterHermes Records release worldBranded route panel
Cultural starter
Hermes Records release world
A culture-facing route that shows release logic, editorial mood and stronger visual authorship can also be templated in the right way.
- Release-first structure
- Editorial depth without chaos
- Stronger worldbuilding than a generic theme lane
Software starterEvaQuant product disciplineBranded route panel
Software starter
EvaQuant product discipline
A sharper product-facing route that proves PixelPiraterij can carry dashboards, hierarchy and operator logic, not just polished brochure pages.
- Interface discipline under the brand layer
- Useful proof for tooling and dashboard routes
- A believable bridge into builder and app logic
03
Where people actually build inside this setup.
The builder story only becomes believable when the path is explicit: choose a starter, brand it, edit it inside a controlled structure and publish it into a real route.
Choose
Pick a route that already matches the audience, product type and commercial rhythm instead of starting from a blank page.
Brand
Set the logo, palette, type and tone so the starter stops feeling generic and starts reading like the client.
Edit
Change sections, copy, media and page order inside a structured setup rather than breaking the system with random edits.
Publish
Preview, launch and grow into managed hosting or deeper studio work when the starter becomes a serious business surface.
04
Make the template-versus-custom decision visible.
This domain should help people decide what kind of route they actually need: a strong starter, a deeper custom trajectory or a live app route inside the hub.
Route frame
Start with a template
Choose this when the route mainly needs a strong front end, fast launch timing and a proven starting structure.
- Best for focused launch surfaces
- Faster route into a credible first version
- Still shaped by audience and tone, not by a generic skin
Route frame
Move into custom
Choose this when the route needs heavier logic, multiple surfaces, deeper operator behavior or a product layer that clearly outgrows a starter.
- Better for deeper product and portal logic
- Useful when systems, automation or multi-surface behavior become core
- Bridges back into the flagship studio cleanly
Route frame
Open the hub
Choose this when the question is no longer what can be built, but which live app or utility should actually be opened or used.
- App shelf instead of capability narrative
- Direct routes into live web versions
- A separate layer for distribution and product access
05
Use the part of the world that matches the job.
This should help someone orient quickly: launch faster, open a utility, or understand the stack before moving into studio work.
Route frame
Launch a site faster
Start from a shaped route, not a blank canvas and not a random marketplace theme.
- Audience-led template directions
- Studio taste carried into faster starts
- Clear bridge back to the flagship build
Route frame
Open a live utility
Use the public-facing tools and proof routes already sitting around the PixelPiraterij stack.
- One harbor instead of scattered links
- Utilities framed by actual role and maturity
- Useful now, expandable later
Route frame
Understand the system
Read the routes before buying the myth. Docs and guides keep the wider story grounded.
- Getting-started logic
- Guides for use and sequencing
- Reference-like clarity without pretending the stack is finished
06
Visible proof keeps the world honest.
The world gets stronger when it shows real template logic, product depth and cultural range instead of hiding behind future language.
Template proofTemplate-backed starts should still feel deliberate.Branded route panel
Template proof
Template-backed starts should still feel deliberate.
The PixelPiraterij suite proves that even a compact entry route can feel shaped when pricing, unlock logic and visual restraint stay aligned.
- Useful as a paid starter instead of a throwaway teaser
- A stronger bridge between product and presentation
- Faster launch logic without cheap velocity
System-facing proofProduct depth matters when the studio says it can build beyond websites.Branded route panel
System-facing proof
Product depth matters when the studio says it can build beyond websites.
EvaQuant brings dashboard logic, hierarchy and operator visibility into the world. That matters because the wider stack needs more than pretty landing pages.
- Signal-first interface patterns
- Operational framing behind the visual layer
- Proof of system thinking under the brand
Culture routeThe world also needs cultural proof, not only utilitarian proof.Branded route panel
Culture route
The world also needs cultural proof, not only utilitarian proof.
Hermes Records keeps the harbor from feeling sterile. It shows that the world can carry atmosphere, release logic and identity without losing structure.
- Culture and utility can live in one system
- Editorial mood with clearer control
- Proof that worldbuilding is part of the stack
07
How this world should behave.
A public system world needs better sequencing than a moodboard. This is the route discipline that keeps the whole thing credible.
Start
Pick the route first: template, app, docs or lab. The point is clarity before spectacle.
Frame
Use the route pages to understand what is public, what is active and what is still maturing.
Bridge
When a route needs heavier custom work or managed hosting, move back into pixelpiraterij.nl without losing context.
Expand
The world should grow out of visible capability, not out of promises that outrun the product.
Next move
If the route needs custom build depth, move from the world back into the studio.
The point of this domain is not to replace the flagship. It is to make the wider system readable and useful before the heavier work begins, then hand off cleanly into the studio or the hub.