Phlo
Phlo compiles its own full-stack language to PHP you can read. The same language writes your routes, drives your DOM, runs your server and manages your fleet.
prop title = 'Phlo Poll'
prop options = ['Phlo', 'Svelte', 'Laravel', 'Rails']
route GET poll => view($this, $this->title)
view:
<main#app.poll>
<h1>$this->title</h1>
<foreach $this->options AS $option>
<a.async href="/vote/$option">$option</a>
</foreach>
</main>
<style ns=app>
.poll a {
display: block
background: $primary
border-radius: 8px
}
</style>Phlo is not just a language and not just a framework. Every layer is built on the previous one, in the same syntax, with the same mental model.
A clean syntax without semicolons that compiles to readable PHP. Routes, views, CSS and logic per class in a single .phlo file.
Guide → 02A backend with resources, ORM and instances. A frontend with phlo.js: an integrated SPA engine, the apply() protocol and extensible browser functionality.
Manual → 03Production on FrankenPHP in worker mode, realtime through phloWS, messaging through phloWA and mail. One coherent server architecture.
Ecosystem → 04The Phlo dashboard manages applications and servers centrally: fleet overview, domains, databases, notifications and visitors. Your entire technical architecture, overseen from one place.
Phlo Dashboard →Five examples of Phlo source next to what the compiler makes of it. No toolchain, no magic: just readable output.
One line dispatches and renders. A route always ends in view(), apply() or location().
prop question = 'Which stack wins?'
route GET poll => view($this->question, 'Phlo Poll')// Compiles to readable PHP:
class poll extends obj {
public $question = 'Which stack wins?';
public static function GETpoll(){
return view(phlo('poll')->question, 'Phlo Poll');
}
}HTML in the same file as the logic. Dot syntax for class and id. Blank line closes the view.
prop question = 'Which stack wins?'
prop options = ['Phlo', 'Next.js', 'Laravel', 'Rails']
view:
<main#app.poll>
<h1>$this->question</h1>
<foreach $this->options AS $option>
<button>$option</button>
</foreach>
</main><!-- Server-rendered HTML: -->
<main id="app" class="poll">
<h1>Which stack wins?</h1>
<button>Phlo</button>
<button>Next.js</button>
<button>Laravel</button>
<button>Rails</button>
</main>Write in your source language. Phlo looks up translations via hash and falls back on the source.
view:
<h1>{en: Which stack wins?}</h1>
<button>{en: Vote}</button><!-- /poll (source language: English) -->
<h1>Which stack wins?</h1>
<button>Vote</button>
<!-- /nl/poll (auto-translated via langs/nl.ini) -->
<h1>Welke stack wint?</h1>
<button>Stem</button>One route serves both sync and async. In async, it sends DOM commands instead of HTML; the client applies them directly.
route both POST poll vote $id {
if (!$option = type_poll::record(id: (int)$id)) return false
type_poll::change('id=?', (int)$id, votes: $option->votes + 1)
if (%req->async) return apply(outer: arr('#results' => $this->results))
location('/poll')
}// Async vote: the server replies with DOM commands,
// the client applies them. No reload, no JS, no API layer.
{
"outer": {
"#results": "<section id=\"results\" class=\"card\">...</section>"
}
}
// A plain browser (no async) gets a redirect to /poll instead.
// One route serves both.CSS in the same file, one line per declaration, no semicolons.
<style ns=app>
.option {
display: grid
grid-template-columns: 1fr auto
gap: 4px 12px
}
.bar {
height: 8px
border-radius: 4px
background: $primary
transition: width .4s
}
</style>/* Compiled into app.css: */
.option {
display: grid;
grid-template-columns: 1fr auto;
gap: 4px 12px;
}
.bar {
height: 8px;
border-radius: 4px;
background: var(--primary);
transition: width .4s;
}The power of Phlo is not in any single layer but in the vertical integration of all of them: the same language that writes your route drives your DOM, runs your server and manages your fleet.
Read the design philosophy →
With Docker you have a running app without installing anything. The installer asks for a name, host and resources and only finishes after a clean build.
Q-AI develops practical products and technical solutions that simplify work and deliver real value. Phlo is the open-source foundation beneath that work.