Sign in to a conference that is already halfway through its year.
No form, no card, no trial clock. DevFlow Conf 2027 is a seeded three-day event: proposals in every state, a review round with real scores, sponsors part-way through their entitlements, an agenda with conflicts. Pick a role and go.
Three roles. Same conference, three different products.
What each person may see is worked out per request. Signing in as the speaker is the only honest way to find out what a speaker sees.
| Role | Password | What you land in | |
|---|---|---|---|
| Organizer / program chair | sbek-organizer@example.com | SbekTest!2027-org | Every event, the proposal board, the agenda, sponsors and the publish queue. |
| Reviewer | sbek-reviewer@example.com | SbekTest!2027-rev | A queue of assigned proposals, a rubric, and the ones a conflict blocks. |
| Speaker | sbek-speaker@example.com | SbekTest!2027-spk | One accepted talk, its room and time, and what is still outstanding. |
It is a shared sandbox, and it gets reset. Anyone reading this page signs in as the same organizer you did, so treat what you type as public. Nothing leaves the demo: with no email provider installed, every message is recorded and never sent.
Five things worth trying, in the order they prove something.
Every one is a claim made elsewhere on this site. Go and check them.
Open the agenda and break it
Drag a session onto a room that is already busy. The conflict appears beside the grid as you drop it, and the publish button stays shut until it is resolved or acknowledged with a reason.
Try to review your own proposal
As the reviewer, find a proposal you are credited on. There is no score box to fill in.
Spend a sponsor's second session slot
On the sponsors screen, watch the used-against-bought count move. Then try to spend one more than the package holds.
Publish the schedule, then roll it back
Publishing writes an immutable snapshot; rolling back points at the previous one. Neither touches the live programme tables.
Look at the outbox
Every message sent or attempted, with its template, recipient and status. The seed installs no email provider, so mail is composed, recorded and stopped.
The same conference, on your laptop, in one command.
The seed the demo runs on ships with the source. One command resets a local database, migrates, seeds the conference, serves it on port 8787 and publishes the schedule.
git clone https://github.com/sameersegal/Podium
cd Podium
npm install
npm run devThen sign in with the credentials above. Running it locally is also the only way to try the integrations: point it at your own Resend key and watch real mail leave.
Found something that does not hold up?
Every claim on this site should be checkable in the demo. If one is not, that is a bug in the site or the product, and both live in the same repository.