Ask at the desk. Nobody needs your card.

Event Schedule is an open-source platform for publishing a shareable event calendar and, when you want it, selling tickets from it. A musician posting gig dates, a venue publishing a lineup and a food truck posting where it will be parked all end up with the same object: one schedule at its own address, with the events on it, ready to send people to or embed in a site you already have.

No. You create a schedule, add events, and share the link. If the details are already written down somewhere, paste the text or drop in a flyer image and AI parsing fills the fields for you to check before you save. That is on the free plan, up to 10 parses a day.

Yes, and the free plan is not a trial that quietly expires. Unlimited events, a mobile-friendly public page at your own address, two-way Google, Outlook and CalDAV sync, sub-schedules, recurring events, free registration with a capacity limit, built-in analytics, the embeddable calendar, backup and restore, and newsletters to 10 recipients a month all cost nothing, permanently. Selling tickets is on the free plan too, through Stripe, PayPal or cash, capped at 25 paid ones a month rather than charged for. The paid plans lift that ceiling and add a short list of other things, and the rate card above sets out exactly which.

Yes, on the free plan. Every schedule has an iframe embed code you copy into your own site. It is a window onto the same schedule rather than a copy of it, so it is current the moment you change an event.

Free gives you the calendar: unlimited events, two-way calendar sync, sub-schedules, recurring events, built-in analytics, the embed, event graphics, and newsletters to 10 recipients a month. Free also sells: 25 paid tickets a month through Stripe, PayPal or any other payment method, scanned at the door, and one bookable appointment type. Pro is $5 a month and takes both ceilings off, then adds the rest of the selling kit: the live check-in dashboard, passes, promo codes, gift cards, add-ons, installment payments, unlimited appointment types, the ticket waitlist, custom fields, webhooks, the REST API, custom CSS, and taking the Event Schedule branding off your public pages. It also raises newsletters to 100 recipients a month.

Enterprise is $15 a month and adds reserved seating for venue schedules (a seating plan drawn once and reused on every date), a custom domain for your schedule, Internal and Unlisted event visibility with an optional password, up to five team members with availability tracking, scheduled graphic emails, event creation over WhatsApp, the AI generators for schedule and event copy, agenda scanning, and newsletters to 1,000 recipients a month. Priority support comes with it.

No. Event Schedule takes no cut of ticket revenue at all. Money moves through your own Stripe or PayPal account, so the only thing off the top is the processor's own fee: Stripe's is currently around 2.9% plus 30 cents a transaction in the United States. The rest is yours, and it lands in your account rather than in ours.

The 7-day trial applies to a paid plan, not to the product. When it ends, the card on file is charged for Pro at $5 a month or $50 a year, or Enterprise at $15 a month or $150 a year. Cancel during the trial and nothing is charged. Cancel later and the schedule drops back to the free plan with every event and every record intact. You lose the paid features, not the calendar.

Yes. There is no contract and no cancellation fee. The schedule reverts to the free plan and stays live at the same address. You can also take a copy with you first: backup and restore is on the free plan, so an export is not something you have to pay to be allowed.

Free and Pro include one team member, which is you. Multiple team members are an Enterprise feature, capped at five, and Enterprise adds an availability tab for tracking who is around on which day. An admin runs the schedule day to day, ticket sales and the door included; a viewer is read-only and sees no sales, but can scan tickets at the door. Being blunt about it, do not sign up for the free plan expecting to invite your whole staff.

Connect Stripe or PayPal, which takes a couple of minutes, then add ticket types to an event with a name, a price and a quantity. Buyers check out from the event page and get an emailed ticket carrying a QR code. The first 25 paid tickets a month are on the free plan; Pro removes the ceiling.

Yes, on every plan, including free. Connect your own PayPal account under Settings, Payment Methods, where the credentials are checked with PayPal before they are saved, then choose PayPal as the event's payment method. The buyer approves the payment on PayPal's own page and the money lands in your PayPal account, with no platform fee. A buyer can pay for tickets to several of your events in one PayPal checkout. Installment plans need Stripe, and gift cards and paid appointments do not offer PayPal. The other ways to take money are Stripe, Payfast for South African rand, Invoice Ninja, a payment link of your own, and cash.

Yes, on every plan. From the Sales page, a Stripe or PayPal sale can be refunded in full or in part, and the money goes back through the provider before the sale is marked refunded, so the page never says money moved when it did not. A partial refund leaves the sale paid and its tickets valid, and the page shows how much has gone back so far. A full refund puts the tickets, and any seats, back on sale. An installment plan is refunded leg by leg, in full only. A sale taken any other way, such as cash, a payment link, Invoice Ninja or Payfast, shows a Mark as Refunded button instead, which records the refund while you return the money yourself.

Yes, as many as the event needs: general admission, early bird, concession, a group rate. Each type carries its own price, quantity, description and sales window, and the window is a pair of exact dates and times rather than a rule about the door. Quantity is counted per occurrence date, so a weekly event does not share one pool of stock across every week.

Each ticket email carries a QR code. Open the scan screen on any phone or tablet, point it at the code, and the ticket is verified and marked as used. A second scan of the same code is caught rather than argued about at the door. Scanning is on every plan, and it needs no dedicated hardware.

Yes, on Pro. The check-in dashboard shows how many people are in against how many sold, broken down by ticket type, with a recent activity feed of names and times. It refreshes itself every ten seconds and works on the phone in your hand at the door.

Yes, with custom fields on Pro. A field can be a short text answer, a longer one, a dropdown, a multi-select, a date or a yes/no switch, and you attach it either to the order or to each individual ticket. Access needs, a meal choice, a shirt size, a school contact: ask at the point of purchase and the answer arrives with the sale.

Yes. Free and paid ticket types sit on the same event, which covers comps, volunteer passes, and a free tier running alongside paid admission.

Yes. Free registration is on the free plan, with an optional capacity limit counted per date, so a weekly session can hold twenty people this Thursday and twenty more next Thursday, and a waitlist for when it fills up is free too. Priced ticket types, payment through your own Stripe or PayPal account and scanning the QR at the door are all on the free plan as well, capped at 25 paid tickets a month. Pro is what removes the cap and adds the live check-in dashboard.

A waitlist button appears in place of the sold-out ticket and people join with a name and an email. If stock comes back from a cancellation or a refund, the next person in line is emailed and has a 24-hour window to buy before the offer passes to the person behind them. The ticket waitlist is on Pro; the waitlist on a free registration is on every plan.

Yes, on every plan, and it is a different list from the waitlist. The waitlist is for a sold-out event; this is for an event whose tickets are not on sale yet, or a visitor who is not ready to buy. They leave just an email address, from the Add to Calendar menu or a quiet link beside the buy button, and get one email when tickets go on sale, one if it is cancelled, a reminder shortly before it starts, and any notice you choose to send if the date or venue changes. Each date of a recurring event is its own list, every email has a one-click unsubscribe that deletes the address, and the event's Tickets panel shows you how many people are waiting. It does not sign them up to your schedule or touch your newsletter allowance.

Yes, both ways, on the free plan. Events you create here appear in the Google Calendar you connect, and events you add there come back here. Google pushes changes over a webhook rather than waiting for a nightly job. Outlook and Microsoft 365 sync the same way, and CalDAV covers the rest. You also choose, per schedule, what should happen locally when an event is deleted in the external calendar: keep it, mark it cancelled, or delete it too.

Yes. Every event page carries add-to-calendar buttons for Google, Apple and Outlook, and the Apple one is the .ics download, so anything that reads a calendar file is covered by the same button. On a recurring event each date gets its own set rather than one link for the whole series. The same menu also offers to subscribe to every event on your schedule: a live feed their calendar app keeps re-reading, so a moved date updates itself, where a downloaded .ics file is a one-off snapshot. It costs them no email address, and it is a different thing from the two-way sync you set up for your own calendar.

Yes, on the free plan. An event can repeat daily, weekly, every few weeks on the days you choose, monthly on the same date, monthly on the same weekday, or yearly. Give the recurrence an end and it stops on its own: a closing date, or after a set number of occurrences. Individual dates can be added or taken out as exceptions, which is how a holiday or a one-off move gets handled without rebuilding the series.

A schedule is the calendar itself, the thing with a name and an address, like The Blue Note or DJ Sarah. Sub-schedules are strands within it that sort and colour-code what is on, such as a series or a strand of programming, so somebody can look at one strand instead of the whole year. Events are the individual dates. One thing worth knowing: a sub-schedule organises, it does not hide. Hiding something is a visibility setting on the event.

Yes, and on the free plan, not Pro. You compose in a block builder starting from a template, pull in your event listings, and send to followers, ticket buyers, a sub-schedule's audience or a list you import. Opens and clicks are reported afterwards. What changes with the plan is volume: 10 emails a month on Free, 100 on Pro, 1,000 on Enterprise, counted per recipient, so one letter to 40 followers uses 40 of the allowance. Uploading your own images into a newsletter is the one part that needs Pro.

The newsletter tool is the email marketing. It has reusable audience segments, imported lists, A/B tests, a scheduled send, and open and click tracking. There is no separate product to buy and no second bill for it.

Some of them do, and the difference matters. Anyone who gave your schedule an email address and confirmed it is emailed a digest when you publish new public events, batched so a season announced in one sitting is one message rather than twenty, and never more often than once every three days. It does not count against your newsletter allowance. Somebody who followed you while signed in to their own account is on a separate list, and that one only ever hears from a newsletter you write yourself. You can switch the automatic digest off per schedule under Settings, Notifications.

Yes, once the address is confirmed. The sign-up panel on a schedule asks for a name and an email address, and confirming the link we send also sets up a passwordless account that follows the schedule; adding a password takes one step. What the panel promises is occasional email updates: a digest when the schedule publishes new events, at most one every three days. Ticking the box at checkout joins the same list without creating an account.

Yes. Turn on event requests and your schedule gets a public submission form. On venue and curator schedules you can also require approval, so nothing appears until you have looked at it. Submissions land in a pending queue and you are emailed when one arrives, and if you decline one, the person who sent it is told.

By default the schedule is public, because being findable is usually the whole point of having one. You decide what appears on it, and every event carries its own visibility setting, so the page can be live while half of what is planned on it is not.

Yes. Draft is on the free plan: the event exists for you and is published nowhere, not on the page, the feeds, the graphics, a newsletter or the calendar sync. Enterprise adds two more options: Internal, which stays members-only for good, and Unlisted, which is off the schedule but reachable by direct link, with an optional password.

Card details never reach us. Buyers pay on the provider's own page: Stripe's checkout, PayPal's or Payfast's, or the Invoice Ninja invoice or payment link you set up. The money lands in your own account with that provider, and Stripe and PayPal are both PCI-DSS compliant. We hold the sale record, not the card number.

No. Your data is not sold, shared or used for advertising. The built-in analytics are first-party and count page views without loading a third-party tracker. If that is still not close enough to the bone, selfhost it and nothing leaves your own server.

When an organizer lists a performer or venue who is not on Event Schedule yet, a page is made for them so the dates have somewhere to point. That page says which schedule created it and that it has not been claimed, credits each date to the schedule that added it, and stays out of search engines until it is claimed. To claim it, press “Claim this page” and sign in with the email address it was made with: you become the owner, and the schedules that already list you keep listing you. If the page carries no contact details, ask the schedule that listed you to send an invitation. And if it is not you at all, “This is not me” takes the page down at once for whoever holds that address, and is recorded for review for anyone else.

Yes. Accent colour, font, background, header image, profile image and a grid or list layout are all on the free plan, as is a logo-wall header that shows the venues you have played. Pro adds custom CSS for anything the settings do not reach, and takes the Event Schedule branding off your public pages. Enterprise puts the whole thing on a domain of your own.

Twelve: Arabic, Dutch, English, Estonian, French, German, Hebrew, Italian, Portuguese, Romanian, Russian and Spanish. The right-to-left languages are laid out right to left rather than bolted onto a left-to-right page.

Yes. Each schedule picks the language it is written in, so two schedules on one account can be in two different languages. You can also nominate one other language to translate into, and event names and descriptions are translated by AI into it with a language switch on your public page. That is free, and it is one target language at a time rather than all twelve at once.

You get counts, not people, and being exact about it: the built-in dashboard reports page views over time, a desktop, mobile and tablet split, which countries those views came from, which domains referred them, and which UTM campaign tags they arrived with. It is on the free plan. What it does not report is any kind of person, not even a unique-visitor number, and it does not load a third-party tracker in order to get one.

There is no Google Analytics integration, on purpose. The built-in dashboard covers views, devices, countries, referring domains and UTM campaigns first-party, so your audience does not get handed to an ad network in order for you to learn that Tuesday was busy.

Yes. Paste text or drop in an image and AI parsing pulls out the name, date, time, venue and description and fills the event form, where you check it before saving. It is on the free plan at 10 parses a day, 50 on Pro and 100 on Enterprise. It fills a form in; it does not publish anything by itself.

Yes, under the Attribution Assurance License. The whole application is on GitHub: read it, file an issue, send a patch, or fork it for something of your own.

Yes. Run it on your own server and it resolves to the Enterprise feature set at no cost, with the data on your own hardware. A selfhosted install even has a couple of things the hosted one does not, such as importing events from a URL or a city search, and one-click updates.

Yes, on Pro. The REST API covers events, schedules, sub-schedules and sales, plus read endpoints for post-event feedback and fan-submitted content, and there are outgoing webhooks for sales, event changes and check-ins.