Roleplay Project
Server Online
Discord
Apply
Roleplay Project
Server Online
Discord
Apply
We're opening Roleplay Project to regional franchise operators — Romanian, Spanish, German, and beyond — who want to run a localised server under our brand, framework and playbook. You bring the language, the community, and the operational drive. We bring the platform, the rules, and the back-of-house. The engagement is structured, confidential, and binding only once both sides sign.
The full FiveM/TypeScript framework, Vue NUI overlay, UCP, bug portal, creator portal, faction systems and operational tooling, licensed for your regional server.
How we actually run an RPP server: moderation policies, the application gate, the economy, safeguarding workflows, faction onboarding, the FiveM-side admin tools. You skip a year of mistakes.
Right to operate under "Roleplay Project · <Region>" with our visual identity, supported by the central marketing site, unified Discord presence, and cross-regional referral.
Framework updates, security patches, schema migrations and new features land in your regional install on the same cadence as the UK origin. Direct access to the engineering team.
Structured onboarding for your senior staff: rules adjudication, ban review, faction lead training, incident response, GDPR/PECR compliance, payouts and creator partnerships.
Shared identity across all RPP regional servers via the central UCP, so a verified player in one city is a verified player in another, and creators carry their codes across borders.
You submit the form below. We come back within five working days to schedule a 30–45 min call. We talk about your region, your community, your motivation, your operating capacity, and whether the franchise model is right for you.
No NDA yetIf the initial call goes well, both sides sign a Non-Disclosure Agreement. With the NDA in place we share the full commercial framework: fees, schedule, revenue share, infrastructure requirements, the operational playbook, and the legal structure of the Franchise Agreement.
NDA in placeWe perform mutual due diligence: KYC on principals, financial verification of your capacity to meet the upfront commitment, references on your community history. If both sides remain comfortable, we sign a non-binding Term Sheet that frames the Franchise Agreement.
Mutual DDThe Franchise Agreement and accompanying schedules are executed. Funds clear. We provision your regional infrastructure, deliver the codebase under licence, run your operator-training programme, and prepare for launch. Each stage has a Statement of Work attached.
BindingTwo reasons. Commercially, the figures shift with the region, the size of your community, the regulatory environment, and the infrastructure your launch will need — a one-size-headline misleads. Operationally, we'd rather you engage because the model fits, not because a number on a web page anchored your expectation. The figures are real, they're meaningful, and they're disclosed in full once the NDA is signed.
The playbook, the rule-adjudication framework, the moderator-onboarding documentation, the framework code, the economy parameters and the financial structure are the entirety of what we have to offer a franchise operator. Sharing those before a mutual NDA is in place isn't commercially sensible. The NDA also protects you: anything you tell us about your community, your finances, your principals and your plans is bound by the same agreement.
The first two regional servers in scope are Romanian and Spanish, with Germany, France, Italy, the Nordics, Brazil and the US as serious near-term candidates. We won't onboard two operators in the same region simultaneously; if you're considering a region you think is already in flight, mention it in the form and we'll be straight with you.
From a signed Franchise Agreement to a regional server live and open, plan on six to twelve weeks. Infrastructure provisioning, codebase delivery under licence, your operator-training programme, soft launch, and the public launch are sequenced across that window. Specific milestones go into the Statement of Work attached to your Franchise Agreement.
Yes, subject to security and operational requirements set out in the Franchise Agreement. We can also host on shared infrastructure operated by Phytoventures Ltd if you'd prefer the hands-off route. Either choice has cost implications which sit inside the commercial briefing.
The franchise programme is the only commercial route. If you'd like to operate at the UK origin server instead, look at the developer applications page (paid engineering roles) or the Content Creator Programme. Both are open without capital commitment.
No. This page, the form submission, and every conversation we have prior to a signed Franchise Agreement are strictly an "invitation to treat" under English law. Nothing on this page constitutes an offer or a representation. The Franchise Agreement and accompanying schedules govern the entire commercial relationship once executed.