You have decided. Now here is the doing.
The rest of this site argues about whether to move. These two do not argue. They are the sequence of commands that puts a conference platform on your own infrastructure, and the sequence that puts your agent in charge of the half of the job nobody enjoys.
Written from the repository, not from memory.
Every command below exists in the source you are about to clone. Every setting named is one you can go and look at. Where nobody has run something in public, the guide says so instead of implying otherwise.
Deploy it to Cloudflare
“What do I actually have to create, and what breaks on the way?”
Six commands for the services, three environment variables, two to ship it, one secret, and the setup screen that makes you the owner. Then the four choices that bite: the plan that decides whether sign-in works at all, the provider that silently turns password sign-in off, the first-pass review that stays off until you say otherwise, and what moving to Postgres would really cost.
Run it with an agent
“Which parts of this can I stop doing by hand?”
Installing the plugin, scoping a key so a leak is an afternoon, and the jobs an agent can take end to end — the funnel, the unreviewed pile, the speakers holding up the schedule, next year's clone. Plus the three things no key of any kind is allowed to do, and why refusing them is the point.