01
Live utilities
Public tools such as QR, vault, focus and password routes grouped into one calmer harbor.
Apps and portals
Live routes
with a calmer
harbor around them.
This lane explains the public-facing utilities and product-adjacent routes around PixelPiraterij. The actual utility suite lives in the dedicated hub, so this world page can frame the system instead of pretending to be the dashboard.
01
What sits in this harbor.
Some routes are already public tools. Others act as product-facing proof that the stack under PixelPiraterij has real depth.
02
Product-facing proof
Lanes like EvaQuant and LumenOS prove the product side is not fictional theater.
03
Future portals
A clearer frame for what can later expand into builder, client or operator-facing layers.
02
What these routes still need to prove.
Useful now, coherent together and able to deepen later. That is the quality bar for the whole public harbor.
Route frame
Useful now
A route belongs here when it already solves something or helps prove the operating model in public.
- Public utility or usable preview
- A clear role inside the wider stack
- No fake product theater
Route frame
World-consistent
Even small routes should feel like they belong to the same harbor instead of looking like unrelated side projects.
- Shared shell language
- Clear route labels
- Warm trust-first framing
Route frame
Able to deepen later
The point is not to freeze these routes where they are. The point is to give them room to evolve into stronger operator layers.
- Future portal logic
- Operator-facing dashboards
- Builder and account adjacency
Next move
The apps belong in the hub. The world explains why they exist.
That separation matters: hub for usage, world for context, flagship for commercial trust. No more blurred route between the three.