Pre-sales & hosting fit
Questions about game selection, memory, storage, migrations, web plans, expected workloads, or whether a service is a practical match.
Build a hosting request →The OutlawCoreStudios Support Center brings launch guidance, service explanations, migration preparation, common answers, and direct contact routes into one place.
Use the route that matches where you are in the process. This keeps technical questions, sales planning, and custom project requests from being mixed together.
Questions about game selection, memory, storage, migrations, web plans, expected workloads, or whether a service is a practical match.
Build a hosting request →Partnership questions, account concerns, accessibility feedback, policy questions, or other non-project communication.
Open the contact form →Website design, graphics, FiveM resources, Minecraft plugins or mods, dashboards, integrations, and multi-service builds.
Build a guided project brief →Service-linked tickets, billing history, attachments, priorities, and technical escalation will live inside the dedicated client platform.
Open the client portal →Useful context helps us understand the issue or request quickly. Sensitive access information should never be placed into a public form.
Secure access should only be arranged after the request is accepted and the correct authenticated process is available.
Read the privacy policy →Start with these practical resources, then move into the complete knowledge base for more detail.
A practical way to estimate memory without treating player count as the only performance factor.
Read article →Organize resources, database exports, configuration files, and licensing details before a host move.
Read article →What to collect before transferring an existing Minecraft environment to a new service.
Read article →Why backup count, retention, frequency, and off-server copies matter more than a single checkbox.
Read article →Public guides, configuration planning, quote intake, contact requests, status visibility, policies, and direct pre-launch communication.
Authenticated tickets, customer identity, service selection, priorities, replies, attachments, billing context, staff assignment, and complete history.
No public form should be treated as an emergency alert channel. Active-service incident procedures will be defined when production hosting enters service.
Use the advanced hosting configurators or the guided project planner to give the team enough context for a meaningful response.