Frequently Asked Questions

Create the event with date, venue and city, then lay out your rooms and set times. Clubs, venues and bars get their own address filled in automatically; clubs can additionally flag a night as an "off-site event" and run it somewhere else. Running something you already do monthly? Import it from Resident Advisor or duplicate the last one, floors included.

Yes. Add as many floors as the night has — a house floor and a techno floor, a garden, a back bar — each with its own line-up and its own genres inside the same event. Floors carry through to duplicated events, recurring series and the printed running order.

Set times live on the event, not in a chat. Move a slot and the confirmed DJ is notified automatically and can accept or decline the new time, so you are not retyping the same message to five people. Everyone on your team sees the same version.

Every night has a house list plus one bucket per confirmed DJ in the line-up. Each DJ fills their own bucket from inside their booking — name, plus-ones, free or reduced entry — so nobody edits a shared sheet. You set the cap: 10 heads per bucket by default, adjustable per bucket. Walk-ins added at the door do not count against a cap. When the list is final you lock it and no more names go on, yours included — walk-ins at the door still work.

You share one link, or the QR code next to it, with whoever works the door. No account, no app, no handing out your password. They see the list, tick people off, add walk-ins and watch the head count, which refreshes about every 15 seconds. The link expires two days after the event, and you can revoke or regenerate it at any time.

You tag them into a slot by name and they get their own guestlist bucket, exactly like a platform DJ. The door list then shows guests per act instead of dumping everyone into the house allocation. Only your team can add names to those buckets, since there is no account behind them.

Set the series up once with its rhythm and every date is created for you, floors included. Switch on "request residents automatically" and each date sends your active residents a booking request — they still accept it, nothing is booked over their head. When a residency ends, the still-pending requests for future dates are withdrawn automatically. Prefer to do it by hand? Duplicating a past event with its slots and genres still works.

Your regulars, kept on the organisation instead of in your head. They appear on your public page, you can slot them into a night without starting a request from scratch, and a recurring series can request them automatically.

Yes. Owners invite people by email, and the link in that email logs them in and joins them to the organisation in one click — no separate sign-up. There are two roles: members work on everything, owners additionally manage the team and can promote or demote each other. The last remaining owner cannot be demoted, so an organisation can never end up ownerless.

There is a printable running order with the slots grouped by floor, for the booth, the bar and the door. The events list exports as CSV and the calendar as ICS. You can also connect Google Calendar, which keeps a separate djstrich calendar of your events and their line-ups up to date.

The day after, we remind you to record how it went — who actually played, and optionally the numbers. That feeds your DJs' track record and your own history, and it unlocks your event analytics.

Free during the beta. Longer term several models are possible, and anything that becomes paid will be communicated well in advance.

DJ name, profile link, city, a bio of at least 50 characters, at least one genre, a mix link (SoundCloud, Mixcloud or similar) and a press photo. That is the whole submit checklist. Rider, price structure and further press material are optional — they do not gate the application, but they improve your quality score.

You control it: a range ("€500–800"), a starting price ("from €400"), on request, or agency rates. "On request" and "agency rates" show no figure at all. A figure you do publish sits on your public profile — it never appears in search results, on the city and genre pages, or in link previews.

Yes. Switch to "undercover" from your dashboard at any time — your profile drops out of search, the directory and the sitemap, but stays fully functional and reachable via your direct link. Switch back whenever you want.

Yes, up to three DJ profiles on one account, each with its own name, genres, bio and listing, switched from the top of your dashboard. They share one calendar — you cannot be in two places on the same night — and one inbox, where every request is tagged with the alias it was for. The aliases are not publicly linked to each other.

You block the dates you cannot make, and promoters see whether a date generally works before they send anything. Confirmed bookings block their day automatically, so you cannot be double-booked for the same night; if a booking falls through, the day frees up again.

Yes. Under your gigs you add off-platform bookings with date, venue and fee. The fee is private — only you ever see it. These gigs appear in your calendar and in "next gigs", and they block the day by default; uncheck that if you want to stay open for something else.

Yes. Enter your Resident Advisor profile and your gig history, follower count and upcoming dates pull in straight away. Your discography comes from Discogs, Bandcamp and Beatport at the press of a button. All server-side, nothing retyped.

Yes. Connect Google once and djstrich creates a calendar of its own for your confirmed bookings, your self-entered gigs and your RA dates, and keeps it up to date. It only ever writes to that one calendar — it cannot read your other calendars, and it never changes them.

Confirmed gigs become performance entries on your profile. Promoters and DJs you have played with can leave public vouches ("would rebook", "smooth payout"). Over time that is a verifiable history rather than a claim in your bio.

A graph of your real performance contacts — who has shared a line-up with you, and with your contacts, across two hops. Link your Resident Advisor profile and it builds itself from your gig history.

That is the point of it. Bio, mixes, releases and every social and streaming link on one page, plus a share popup with a branded QR code for flyers, story and square cards to download, and a caption ready to copy. It replaces the link-in-bio list.

Listing is free during the beta. Pricing for later phases will be communicated in advance.

No payment processing, no invoicing, no contracts with e-signature, no ticketing, and no public star ratings or reliability scores for DJs. These are not missing features waiting for a sprint: money and paperwork stay between promoter and DJ, and publicly scoring named people is the wrong instrument for a scene this size.

Because an open directory of thousands of stale profiles is worse than a small one that works. Manual review keeps out empty accounts and keeps a search result worth acting on. It costs new DJs a few days, and we think that trade is right.

At /scene and the city pages, confirmed gigs build a public network: who has played with whom, performance histories and vouches. It makes the real context visible without exposing private booking details.

A public feed of what just happened in the scene: new residencies, confirmed bookings, open calls going live, city milestones, awards and public vouches. Only things that are already public end up there.

Yes. All booking threads on the platform can be viewed by the administration. This serves quality assurance, dispute resolution and checking for violations of the terms of service. Every admin access is logged (audit log). We state this explicitly because we believe it should be communicated transparently — not buried in footnote 47 of the terms.

All data sits with Supabase on EU servers. Analytics (PostHog) only run once you consent. Details are in the privacy policy.

Yes. For account deletion requests, please write to [email protected]. We carry out a soft-delete in accordance with GDPR Art. 17. Some data may be retained in anonymised form for legal reasons, for example booking history.

Every release is written up in plain language at /changelog, linked from the version number in the footer.

By email to [email protected]. We are in the beta and prefer direct feedback to polite silence.