Event Schedule
Every colophon answers three questions.
A colophon is the note at the back of a book: who printed it, what it was set in, and the terms you may reuse it under. Software almost never prints one. Here is ours, and none of it has to be taken on trust. The source is public, you can run the whole thing on your own server, and we take nothing from your ticket sales.
Imprint
- Who made it
- The team behind Invoice Ninja.
- What it is made of
- Laravel, Vue and MySQL, all of it public.
- What you may do with it
- Read it, fork it, run it yourself, and sell tickets with no cut taken.
Attribution Assurance License · github.com/eventschedule
B The three questions
Each one has an answer you can go and check.
Question one
Who made it
The same team that built Invoice Ninja. The license itself carries the attribution clause that names the author, which is why this page can be specific rather than vague about it.
Read about the makersQuestion two
What it is made of
Laravel on the server, Vue on the front end, MySQL underneath, and all of it on GitHub. The code that runs the hosted service is the code you can download.
Open the repositoryQuestion three
What you may do with it
Run it on your own server, where a selfhosted install is treated as Enterprise. Sell tickets through your own Stripe account, where the platform fee is zero.
See the terms in the imprintThree claims, three places to verify them. That is the whole argument of this page.
C The imprint
Set in Laravel. Licensed for reuse. Sold with no cut taken.
The back page of a book prints the facts that outlast the marketing. These are ours, and every one of them points at somewhere you can check it.
| Field | Record |
|---|---|
| Publisher | Event Schedule, built by the team behind Invoice Ninja, a source-available invoicing platform. invoiceninja.com |
| License | The Attribution Assurance License. The full text is the LICENSE file in the repository, not a summary of it. Read the license |
| Source | Public on GitHub. Read it, fork it, or open an issue against it. 53 stars so far. github.com/eventschedule |
| Set in | PHP and Laravel on the server, Vue on the front end, MySQL underneath. No part of it is a black box you cannot open. |
| Impression | Hosted at eventschedule.com, or selfhosted on hardware you control. A selfhosted install resolves to the Enterprise tier, so no paid plan holds anything back from it. How selfhosting works |
| Platform fee | None, on any plan. Tickets are sold through your own Stripe account and settle into it directly, so past Stripe's own processing charge the money is yours. How ticketing works |
| Free plan | $0, with no credit card and no expiry. One team member. Pro is $5 a month and Enterprise is $15. See the plans |
| Analytics | Opt-in. Analytics, advertising and personalization signals are set to denied until you press Allow in the cookie banner, and declining sets no analytics cookies at all. Privacy policy |
| First edition | The first commit landed in July 2024, and the repository has carried every change since in public. |
D Why it was set
Making event sharing effortless.
Event Schedule was created to solve a simple problem: making it easy for anyone with events to share them with their audience.
Whether you are a musician with upcoming shows, a venue with a packed calendar, a curator aggregating local happenings, or a food truck appearing at a different spot each day, you deserve a simple, professional way to let people know where you will be.
Sharing your schedule should not require expensive software or technical expertise. That is why Event Schedule is free, fast and easy to use, and why the version you can download is the version we run.
E Who it is set for
Three kinds of schedule, one book.
However you share your events, Event Schedule is built to work for you. There are only three schedule types, and everything else is a variation on them.
For Talent
01Share your upcoming shows, appearances and locations with the people who follow you. Musicians, DJs, comedians, dancers, magicians, food trucks: anyone whose audience needs to know where to find them next.
Read the chapterFor Venues
02Keep one calendar current and public, so visitors can see what is coming up and buy tickets straight from the schedule instead of hunting for a listing.
Read the chapterFor Curators
03Aggregate events from several schedules and publish a guide to what is happening in your area or your niche, with the originals still credited.
Read the chapterNot sure which one fits? Browse every use case and pick the closest.
F Two impressions
The same book, printed on two presses.
Open source only means something if you can actually run the thing. These two columns are the same application. The difference is whose machine it is on.
Recto · we run it
eventschedule.com
Sign up and you have a schedule at your own subdomain in a couple of minutes. Updates, backups and the mail queue are our problem.
- A free plan that sells 25 tickets a month, with no expiry and no credit card Free
- Unlimited ticket sales and the check-in dashboard for $5 a month Pro
- Your own domain and up to five team members for $15 Enterprise
- Zero platform fees on ticket sales, settling into your own Stripe account
Verso · you run it
Your own server
Clone it, point it at a MySQL database and it is yours. The data never leaves the machine, and there is nobody to ask permission from.
- Every paid-tier feature, because a selfhosted install resolves to Enterprise
- One-click app updates, which only exist on selfhosted installs
- Importing events from a URL or by city, also selfhost-only
- No monthly newsletter allowance, because that limit only applies to hosted schedules
G Standing rules
What we believe in, pinned to the press.
A press keeps standing instructions pinned by the machine: the things that do not change between jobs. These are ours.
Pinned at the press · do not take down
-
Free is not a trial
The free plan has no expiry date and asks for no card. Unlimited events and schedules, recurring events with date exceptions, sub-schedules, free registration with a capacity limit, two-way calendar sync, the embeddable calendar and built-in analytics all sit on it, and so does selling tickets, up to 25 paid ones a month.
-
Your data is yours
It is never sold and never shared with third parties. Site analytics are opt-in and stay denied until you press Allow. Export the whole schedule whenever you like, and if that is still not enough, selfhost and it never leaves your server.
-
Say what it does not do
A short product done properly beats a long list done badly. When something is missing we would rather print it than let you find out in the middle of an event, which is what the next section is for.
H Errata
The slip that says what is not here.
Books ship an errata slip tipped in at the front. Software rarely does. Five things Event Schedule does not do, so you can decide with the whole picture rather than half of it.
Errata · please note
-
There is no seat map.
A ticket type carries a name, a price, a quantity and a sales window. Buyers are not choosing a specific seat, and there is no seating chart to draw.
-
Followers are not emailed automatically.
Nothing goes out when you add an event. Following gives you a list you can write to: you compose the newsletter and press send. Ticket buyers are the exception, and they are emailed when an event they bought for changes or is cancelled.
-
Nothing checks for double bookings.
Two events at the same time in the same place will both simply appear. The calendar does not object, and it will not warn you.
-
Newsletter allowances count recipients.
Not sends. One newsletter to a hundred followers uses a hundred of the allowance: 10 a month on Free, 100 on Pro, 1,000 on Enterprise.
-
The free plan is one team member.
Multiple team members, capped at five, are an Enterprise feature. Selfhost and you have them, because a selfhosted install is Enterprise.
If one of these is a deal-breaker, better to know now. Read what it does do and judge the whole thing.
I The makers
Built by the team behind Invoice Ninja.
Same people
Same approach
Event Schedule is made by the same team that built Invoice Ninja, a source-available invoicing platform used by businesses around the world. Both projects are run the same way: the source is public, selfhosting is a first-class option rather than an afterthought, and the paid plans exist to fund the work rather than to hold the useful parts hostage.
That is also why the license here is unusual. The Attribution Assurance License requires that the author's name travels with the code, which means the answer to "who made this" is written into the software itself and not just onto a marketing page.
J The source
Free and open source.
Event Schedule is open source under the Attribution Assurance License. Selfhost it on your own server, contribute to the codebase, or just use it free forever. The repository is public and the history goes back to the first commit.
K Questions
What people ask before they trust it.
Is Event Schedule really free?
Yes, and not as a trial. Unlimited events and schedules, recurring events with date exceptions, sub-schedules, free registration with a capacity limit, two-way Google, Outlook and CalDAV sync, the embeddable calendar and built-in analytics are all on the free plan, along with selling up to 25 paid tickets a month and scanning them at the door, with no credit card and no expiry. Unlimited ticket sales and the check-in dashboard are on the Pro plan at $5 a month, multiple team members are on Enterprise at $15, and the free plan is one team member.
What license is it under, and where is the source?
The Attribution Assurance License. The full text is the LICENSE file in the repository at github.com/eventschedule/eventschedule, which is public: you can read the code that runs the hosted service, fork it, or open an issue against it.
Can I run it on my own server?
Yes. Selfhost it and the database sits on hardware you control. A selfhosted install resolves to the Enterprise tier, so unlimited ticket sales, the API, custom CSS, multiple team members and every other paid-tier feature is included, and two things exist only on a selfhosted install: one-click app updates and importing events from URLs or by city.
Do you take a cut of ticket sales?
No. Event Schedule charges zero platform fees. You connect your own Stripe account and the money settles into it directly, so past Stripe's own processing charge nothing is taken. Invoice Ninja works as an alternative payment route on the Pro plan.
Who is behind it?
Event Schedule is built by the team behind Invoice Ninja, a source-available invoicing platform. The attribution clause in the license names the author, which is an unusual thing to write into a license and the reason this page can be specific about who made it.
What happens to my data?
It is never sold or shared with third parties. Site analytics are opt-in: analytics, advertising and personalization signals are denied until you press Allow in the cookie banner, and if you decline, no analytics cookies are set. When somebody follows your schedule or buys a ticket, you see their name and email so you can reach them, and that is the only sharing involved. Selfhost and none of it leaves your server.
Something not answered here? Ask us directly or open an issue on GitHub, where the answer stays public.
Now put your own name on a page.
Create your free schedule today. No credit card required, and nothing taken from your ticket sales.
Free forever · open source · zero platform fees