Skip to main content
After you buy ImplAI on Whop, an invitation to the private source code repository is sent automatically to the same email address you used at checkout, usually within a few minutes. That invitation is where your setup begins. By the end of this page you’ll have your own copy of the codebase under your personal GitHub account, which is what you’ll deploy in the next steps.
The invitation expires after 7 days, and GitHub only lets it be accepted by an account that has that exact email address verified on it. Use the same address you purchased with.
1

Open the invitation email

Find the email from GitHub with the subject inviting you to join the ImplAI-Code organization, and click Join @ImplAI-Code.
GitHub invitation email with the Join @ImplAI-Code button

The invitation is sent to the email address you used at checkout.

2

Accept the invitation

The button takes you to a GitHub page confirming the invitation. Click Join ImplAI-Code.
GitHub page reading You've been invited to the ImplAI-Code organization, with Join and Decline buttons

GitHub's confirmation page for the organization invitation.

Clicking Join @ImplAI-Code sends you to GitHub’s account creation flow instead. Create your account using the exact email address you purchased with, and you’ll land on the GitHub home page.
GitHub home page shown after creating a new account

After creating your account you land here, not on the invitation page.

That first click didn’t actually join you to the organization, because GitHub had no matching account to attach the invitation to yet. Go back to the invitation email, click Join @ImplAI-Code again, and continue with this step as described above.
3

Open the repository

You’re now a member of the organization and you’ll land on its page, where the private ImplAI-ecosystem repository is listed. Click on it to open it.
ImplAI-Code organization page listing the ImplAI-ecosystem repository

The organization page, showing the repository you now have access to.

4

Create your fork

You now have read access to the source code, but you need your own copy to deploy and to receive updates. That copy is called a fork.At the top right of the repository, click the arrow next to Fork, then click Create a new fork.
ImplAI-ecosystem repository with the Fork dropdown open showing Create a new fork

Use the dropdown arrow next to Fork, then Create a new fork.

5

Name and confirm the fork

The Owner dropdown decides where your copy lives, and it must be your own personal GitHub account, the one named after your username. Do not select ImplAI-Code if it appears in that list: that’s the organization the original code belongs to, you only have read access there, and a copy placed inside it wouldn’t be yours to deploy. Everything from here on, including connecting Vercel in the next steps, expects the fork to sit in your personal account.You can confirm you got it right before submitting: at the bottom of the form GitHub displays You are creating a fork in your personal account.Then change the Repository name to something you’ll recognise later, such as Forked-ImplAI-ecosystem. GitHub confirms underneath that the name is available. Leave Copy the main branch only checked and the description empty, then click Create fork.
GitHub Create a new fork form with the repository name set to Forked-ImplAI-ecosystem

Renaming the fork makes it easy to tell apart from the original repository later.

6

Check that the fork worked

GitHub redirects you to your new repository. You should see your chosen name at the top, and underneath it a line reading forked from ImplAI-Code/ImplAI-ecosystem, which confirms the copy is linked to the original.
Forked-ImplAI-ecosystem repository page showing the forked from ImplAI-Code/ImplAI-ecosystem label

The forked from line confirms this is your own copy of the source code.

Never edit the code in your fork. Everything you need to configure is done through the providers in this course, and keeping your fork untouched is what lets you pull in future updates from the original repository without conflicts.

What’s next

Your own copy of the codebase is ready to deploy. Next you’ll buy the domain your platform will run on, and create the professional email address you’ll use to sign up for every other service in this course.