Beta access and invitations
Memberside is in private beta, and public registration is closed. This page explains how to get an account and what to expect once you have one.
Joining the waiting list
Section titled “Joining the waiting list”Go to memberside.app/beta and submit the form. It asks for your email, roughly how many members your community has, and which plugins you run.
The plugin question is the one that matters. Memberside builds screens from specific plugins, and the answers decide what gets built next — so list what you actually have installed, including extensions.
Being invited
Section titled “Being invited”Invitations go out in batches. When yours arrives it contains a link that lets
you set a password and sign in; there is no separate sign-up step, and visiting
/sign-up redirects to the waiting-list form.
The link creates your account on first use. If it expires before you get to it, reply to the invitation and it can be reissued.
What you get during the beta
Section titled “What you get during the beta”Your invitation puts the account on the tier agreed with you. Without one, an account is on Free, which is a real, non-expiring tier rather than a lockout — one app, three builds a month, and every feature screen your site’s plugins support. There is no trial.
Paid plans are open. When you reach a limit, the Upgrade button in the builder takes you to Billing, where you can buy Pro or Unlimited, or add a build pack, through PayPal.
See Plans and limits for what each tier includes, and Add-ons and build packs for everything sold alongside them.
Signing in
Section titled “Signing in”After your account exists, sign in at
build.memberside.app. The builder runs
on that subdomain; memberside.app is the marketing site and will send you
across.
You can also sign in with Google or GitHub if you set that up, or with the email and password from your invitation.
Testing a beta build of the plugin
Section titled “Testing a beta build of the plugin”The Downloads page has a Beta releases section, collapsed and off to one side. A beta is published so it can be tested, and it can change or be withdrawn before it ships — put one on a staging site, not the site your members use.
Each beta shows whether its build produced an installable file. A build that failed is listed with no download, so you can tell a release that is not coming from one you have missed.
Betas are never offered to a site by the updater. You install one deliberately or not at all, and a site running one is offered the next stable release in the ordinary way.
Quickstart takes you from a signed-in account to an installable app.