memberside.app

Licence FAQ

What a plan covers, how many apps and sites you can run, how renewals and cancellations work, and who owns the code.

What does a plan actually cover

A plan covers the builder and the builds: how many apps you can keep, and how many times you can compile them in a month. Pro allows five apps and thirty builds a month; Unlimited caps neither.

Three things are separate subscriptions, because they cost us per gigabyte and per message rather than per app: Media CDN, Real-time and Push Notifications. Every paid plan includes a starting allowance of each, which is enough for a small community to run on indefinitely.

What no plan includes is an Apple Developer or Google Play Console membership. Those are paid to Apple and Google directly, and the account has to be yours — see the question about store accounts in the Installation FAQ.

How many WordPress sites can I connect

One app connects to one site. The limit that matters is the app limit on your plan, so five apps on Pro means up to five connected sites.

Staging and production count separately if you connect both. Many people connect staging only while they are building, then repoint the app at production before the first release, which uses one app rather than two.

How do renewals and cancellations work

Subscriptions renew automatically — monthly or annually, whichever you chose — and you can cancel from Billing in the builder at any time.

Cancelling takes effect at the end of the period you have already paid for rather than immediately, so the rest of the month or year is yours to use. After that the account is on Free: nothing is deleted, and anything already over Free’s limits stays as it is but cannot grow.

Downgrading between plans works the same way. If a downgrade would leave you over the new plan’s app limit, choose which apps to keep before the change lands, or we will hold the account at the higher tier and ask.

Can I get a refund

Ask. The Free plan exists so that nobody has to buy a plan to find out whether it works, but if you have paid for something you could not use, open a ticket under Pre-sales and billing and tell us what happened.

For an annual plan cancelled early we will normally refund the unused months. For a monthly plan we will normally refund the current month if you have not started a build in it.

An upgrade charge — the difference you pay to move up mid-period — is not refunded once you have run a build on the upgraded plan.

Build packs and add-on tiers (Media CDN, Realtime, Push) are not refunded when you cancel. Cancelling stops the next payment, and you keep what you paid for until that month ends. If you cancelled one you never used, ask us.

Is Memberside open source

Part of it. The Memberside WordPress plugin is licensed under the GNU General Public License, version 3, like the WordPress code it runs beside. You can read it, change it and redistribute it under that licence.

The builder, the build pipeline and the app code it generates are not open source. You own the app you publish: its listing, its bundle identifier, and your content, branding and member data. The templates and scaffolding the app is generated from stay ours. Section 5 of the Terms & Conditions sets this out, including what happens to that code if we stop operating. See the next question.

What happens to my apps if Memberside shuts down

The Terms & Conditions commit us to a way out. If we permanently discontinue the Service:

  • We give you at least 60 days’ notice by email.
  • During that period you can request a source-code export of each app on your account, in the state it was last built.
  • You get a perpetual, non-exclusive, royalty-free licence to use, modify, build and publish that code for your own apps. You may not resell or redistribute it as a template or an app-building product.

The hosted services we operate stop when the Service ends: push notifications, realtime messaging and media delivery. The exported code comes as it is, without support or updates, so an app that relies on those services needs a replacement for them before its next release.

None of this applies if the Service is transferred to a successor that keeps operating it. In that case the Service carries on, and so does your account.

Your published apps are yours either way. They sit in the stores under your own developer accounts, and nothing we do removes them.

Not answered here? Open a ticket and we will reply by email — and if the question turns out to be a common one, it ends up on this page.