Your first steps with Volyx
This guide walks you through the normal Volyx workflow from your first sign-in to a running server.
1. Sign in to Volyx
Start by signing in to your Volyx account. After signing in, you can access your dashboard, servers, Coins, account settings, support tools, and other features available to your account.
The Dashboard is the main starting point outside an individual server. From there you can create hosting and open existing services.
2. Check your Coin balance
Supported Volyx server creation and renewal use Volyx Coins.
Before creating a server, check your current balance and compare it with the Coin cost shown by the creation page.
Always use the balance and Coin cost displayed by your Volyx panel as the current source of truth.
3. Get Coins if needed
If you do not have enough Coins, open the Free Coins area and use one of the earning methods currently available to your account.
4. Create your first hosting service
Open the hosting creation page and choose the options that match the project you want to run.
Choose the hosting or workload type that matches your project.
Select JavaScript, TypeScript, Python, Java, or another supported runtime shown by the creation page.
Pick a version compatible with your project and its dependencies.
Review the available CPU, RAM, disk, and other resources.
Use a clear name so the service is easy to recognize later.
Review the displayed Coin cost before confirming creation.
Check the runtime, version, resources, server name, and Coin cost before creating the service.
5. Wait while the server is prepared
After creation, Volyx may need a short time to prepare the server, apply its environment, and make the service available.
If you see the preparation screen, wait for the process to finish instead of repeatedly creating another server.
The preparation screen is expected while the service is being set up. Continue once Volyx makes the server available.
6. Open your server
Once the service is ready, open it from your server list. You will enter the dedicated server workspace.
The main Server section contains:
- Overview — general server state and details.
- Console — live process output and supported commands.
- Files — your project files and editor.
- Config — runtime, version, and project startup configuration.
- Settings — server-level management options.
7. Upload or prepare your project
If you already have a project, move its files into the server using the workflow that fits the project.
8. Configure the runtime
Open Config and verify that the server is using the correct runtime and version for your project.
The most important values usually include:
- Runtime family.
- Runtime version.
- Main or entry file.
- Project-specific startup configuration.
For TypeScript projects, use the supported TypeScript entry files such as .ts, .mts, or .cts.
9. Install dependencies
Most application projects depend on external packages. Install the dependencies required by your project before expecting it to start correctly.
Smart Terminal is useful for package manager commands and build steps when they are required by your project.
If dependency installation fails, read the first useful error instead of repeatedly running the same command.
10. Add Secrets and environment values
Many projects require tokens, API keys, database credentials, or other private values.
Use Secrets or supported environment variables instead of hard-coding private credentials into public project files.
Never place bot tokens, passwords, database credentials, or API keys in screenshots, public repositories, or public support messages.
11. Start the server
When the files, runtime, dependencies, and required environment values are ready, start the server from Console.
Watch the live output while the service starts. A successful startup normally means the process remains running without a fatal error.
12. Check that everything works
Do not stop at seeing the server marked as running. Confirm that the application itself is behaving as expected.
Look for startup errors, warnings, or repeated failures.
Check CPU and memory behavior while the project runs.
Confirm the application is listening on the expected allocation.
If this is a web service, verify the domain only after the application works on its assigned port.
13. Create a backup
Once your first working setup is ready, create a backup if backups are available for the server.
This gives you a known working state before future updates, migrations, or major configuration changes.
If something fails
Avoid changing many settings at once. Work through the problem in a predictable order.
Read the first meaningful error.
Confirm the runtime, version, and main file.
Check whether required packages installed successfully.
Verify required environment values are present.
Use the exact error and ask for the next troubleshooting step.
Open a ticket if the issue needs direct staff review.
First server checklist
Next step
Now that you understand the basic workflow, continue with Create Hosting for a closer look at the server workspace and its sections.