Skip to main content

Colophon
Open source event management platform
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 makers

Question 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 repository

Question 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 or PayPal account, where the platform fee is zero.

See the terms in the imprint

Three 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.

The Event Schedule imprint: publisher, license, source, stack, hosting, fees, plans, analytics and first edition
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. 102 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 or PayPal account and settle into it directly, so past the processor's own 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 First-party. Visits are counted as daily totals without a cookie, the live view that identifies a visitor waits until you allow analytics in the cookie banner, advertising and embedded content wait for a separate choice, and declining sets no analytics or marketing 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 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 with unlimited free registration, no expiry and no credit card Free
  • Tickets with a price on them 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 or PayPal account
Compare the plans

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
  • A daily automatic import from a list of URLs, filtered by city, also selfhost-only
  • No monthly newsletter allowance, because that limit only applies to hosted schedules
How selfhosting works

F The terms in practice

Open source, read the way a buyer reads it.

“Open source event management platform” is easy to print and easy to stretch. For an organizer choosing one, it comes down to four questions. Here is each answer, with the file or page that settles it.

The license

What you may do, and what you owe

The Attribution Assurance License is OSI-approved and adapted from BSD. You may use, change and redistribute the code, as source or as a built program, and nothing in it limits you to non-commercial use. What it asks in return is attribution: the license text travels with any copy you pass on, a built version shows the author's name, Event Schedule and the project address, and nobody may use the author's name to promote a product made from it without permission. That is why a selfhosted install keeps a small Event Schedule credit on its guest pages.

Read the LICENSE file

Where it runs

Hosted or on your server, the same code

On eventschedule.com there is nothing to install: the free plan has no expiry, and keeping the servers up is our job. On your own server you need PHP 8.2 or newer, MySQL 5.7+ or MariaDB 10.3+, Apache or Nginx, HTTPS and one cron entry. Docker, Softaculous, or a release zip with a setup wizard in the browser gets you there, and every paid feature is on. The one thing a selfhosted install does without is a separate domain per schedule, because the whole install already sits on a domain you chose.

Read the installation guide

Your data

How you take it with you

Backup and restore is on every plan. It exports each schedule you can edit, with its events, tickets and sales, and the images if you ask, as one file that another install imports as new schedules, so nothing there is overwritten. The iCal and RSS feeds are public on every plan, and Pro adds the sales CSV export and a REST API with an OpenAPI description. On a selfhosted install the database itself is yours, and moving the whole install is a database dump plus the storage folder and the .env file.

How backup and restore works

Maintenance

Who keeps it going

The team behind Invoice Ninja, in public. Releases are published on GitHub, and a selfhosted install checks once a day for a new one and updates in one step from the admin panel, migrations included. It sends no usage reports and makes no license check. Bugs and ideas go in as GitHub issues, pull requests are welcome, and a translation fix made in an install's own translation manager can be shared back upstream.

Open the issue tracker

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

  1. 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 nothing counts how many places you keep. Putting a price on a ticket is the one thing Pro is for.

  2. Your data is yours

    It is never sold, and it reaches only the service providers that run the platform, and advertising partners only with your consent. Analytics that identify a visitor are opt-in and stay off until you allow them. Export the whole schedule whenever you like, and if that is still not enough, selfhost and it never leaves your server.

  3. 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. Eight things Event Schedule does not do, so you can decide with the whole picture rather than half of it.

Errata · please note

  1. Seat maps are Enterprise only.

    On every other plan a ticket type carries a name, a price, a quantity and a sales window, and buyers are not choosing a specific seat. Drawing a room and selling the seats in it is the one part of ticketing that sits behind the top plan, and the room is drawn on a venue schedule, because only a venue has one.

  2. Refunds move money on Stripe, PayPal and Razorpay only.

    From the Sales page a Stripe, PayPal or Razorpay sale can be refunded in full or in part, and the money goes back through the provider before the status changes. Payfast, Invoice Ninja, a payment link and cash can only be marked as refunded, which records it without moving anything. Either way the ticket buyer gets no email about it from us, so that message is yours to send.

  3. PayPal takes ticket orders and bookings, not every payment.

    Installment plans are Stripe only, and gift cards cannot be paid through PayPal either. A ticket order can, including a multi-event cart, which PayPal charges as one payment, and so can a paid appointment.

  4. Only subscribers get the automatic digest.

    Publishing new events emails the people who left you an email address and confirmed it, at most one digest every three days. Somebody who only pressed Follow while signed in is on a different list, and that one is reached only by a newsletter you write yourself.

  5. Nothing warns you about a clash on the calendar.

    Two ordinary events at the same time in the same room will both simply appear, and nothing objects. Bookable appointments are the exception: an appointment slot disappears the moment anything on that schedule occupies the time, synced calendar entries included.

  6. 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 automatic new-event digest and the notices sent to people waiting on a single event sit outside that count, because the promise there was made to the reader rather than to you.

  7. The free plan is one team member.

    Multiple team members are an Enterprise feature, capped at five people on eventschedule.com, you included. Selfhost and you have them with no cap, because a selfhosted install is Enterprise.

  8. "Unlimited events" has a daily ceiling on the hosted site.

    Not a plan feature, a rate limit: a schedule on eventschedule.com can create 500 events in a day, 1,000 on Enterprise and 100 while a Pro trial is running, with a wider ceiling across every schedule one owner runs. Nothing about a real programme comes near it, and a selfhosted install has no ceiling at all because there is nobody else to protect it from.

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 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 and no monthly ceiling, two-way Google, Outlook and CalDAV sync, the embeddable calendar, built-in analytics and scanning a ticket at the door are all on the free plan, with no credit card and no expiry. Selling a ticket that carries a price, 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 selling tickets at a price, the API, custom CSS, multiple team members and every other paid-tier feature is included. The one exception is a custom domain per schedule, which a selfhosted install has no need of because the whole install already sits on a domain you chose. Two things exist only on a selfhosted install: one-click app updates and a daily automatic import from a list of web addresses.

Do you take a cut of ticket sales?

No. Event Schedule charges zero platform fees, on every plan. Putting a price on a ticket is the Pro step on eventschedule.com (a selfhosted install has it already): you connect your own Stripe or PayPal account and the money settles into it directly, so past the processor's own charge nothing is taken. Payfast, Razorpay, an external payment link, cash at the door and Invoice Ninja are the other routes. A refund comes out of the same account: from the Sales page a Stripe, PayPal or Razorpay sale goes back in full or in part through the provider.

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. It reaches only the service providers that run the platform and, only with your consent, any advertising partners the privacy policy names; the policy lists every one. Analytics and marketing cookies are opt-in: nothing optional is stored or loaded until you allow it in the cookie banner, and declining keeps it that way. When somebody follows your schedule or buys a ticket, you see their name and email so you can reach them. Selfhost and none of it leaves your server.

What does "open source event management platform" mean for Event Schedule?

That the whole application, the same code that runs eventschedule.com, is public on GitHub under the Attribution Assurance License. You can read it, change it, run it on your own server with every paid feature but per-schedule custom domains switched on, and take your schedules out with the backup export on any plan. It does not mean everything on the hosted service costs nothing: there the free plan is permanent, and charging for a ticket is what Pro is for.

Can I modify Event Schedule, or use it for a business?

Yes. The license permits use, modification and redistribution, as source code or as a built program, and it does not limit you to non-commercial use. Its conditions are about attribution: keep the license text with any copy you pass on, show the author's name, "Event Schedule" and the project address in a built version, and do not use the author's name to promote what you build without permission. An install can even run as a service for other organizers, with its own plans and billing, and on such a platform the Event Schedule credit stays on every schedule, whatever plan it is on.

Who maintains it, and how does a selfhosted install get updates?

The team behind Invoice Ninja, in the public repository, which has carried every change since its first commit in July 2024. Releases are published on GitHub. A selfhosted install checks once a day for a new release number, and an instance admin updates it in one step from Settings, App Update, or by running php artisan app:update on the server, which installs the release, runs any new migrations and clears the caches. Take a backup of the database, the storage folder and the .env file first.

Does a selfhosted install report back to anyone?

No usage reports and no license check. Left as installed, it makes two plain downloads on its own: GitHub once a day for the latest release number, and DB-IP once a month for the free country-level database behind the analytics country breakdown. Crash reports reach the developers only if you tick the box in the setup wizard, and every other service, from your mail server to Stripe or an AI provider, is contacted only once you add its credentials.

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.

.eventschedule.com
Start for free

Free forever · open source · zero platform fees