Build, deploy, and operate with confidence

Create your workspace

Sign up, verify your email, and open the Qixla Cloud dashboard.

• Create your account from the registration page.
• Verify email access and complete profile basics.
• Review available products and region options.

Choose your workload

Pick the right template for bots, game servers, web apps, or custom services.

• Select a product that matches your runtime needs.
• Confirm resource profile based on expected traffic.
• Pick the closest region for lower latency.

Configure runtime settings

Set startup command, environment variables, and service ports before first launch.

• Add required environment variables and secrets.
• Set correct start command and runtime version.
• Validate exposed ports and network rules.

Deploy and validate

Launch your service, check logs, and verify health using a real request.

• Trigger initial deployment from the panel.
• Watch build and boot logs for startup errors.
• Run an endpoint or gameplay test after launch.

Enable reliability controls

Turn on backups, add alerts, and document your recovery workflow.

• Schedule automatic backups and retention policy.
• Configure incident alerts and support routing.
• Store rollback steps in your internal runbook.

Projects and Services

Group related workloads into clear projects. Keep development, staging, and production isolated for safe iteration.

Build and Runtime

Build step installs dependencies and compiles assets. Runtime step launches your process with environment values.

Environment Variables

Keep secrets and configuration outside source control. Rotate credentials regularly and scope access by environment.

Volumes and Persistence

Persist world data, uploads, and generated assets in dedicated paths to survive restarts and redeployments.

Backups and Recovery

Use scheduled backups for critical services and test restore paths before incidents occur in production.

Monitoring and Logs

Track startup events, error logs, and runtime metrics continuously. Operational clarity shortens incident time.

• Set token and required API keys as environment variables.
• Install dependencies during build step.
• Use a single foreground process for container health checks.
• Enable auto restart and inspect logs after each deploy.

Tip: Do not hardcode bot tokens in repository files. Rotate keys immediately if leaked.

• Pick a plan with enough RAM for player count and mods.
• Keep world folder and plugin data on persistent storage.
• Set regular backups before plugin or version changes.
• Update server software in a staging clone first.

Tip: Major version upgrades can break plugins. Validate compatibility before applying to production worlds.

• Define install, build, and start commands explicitly.
• Attach domain and configure SSL once service is stable.
• Set health check endpoints for fast failure detection.
• Use separate environment values for staging and production.

Tip: Cache dependencies and artifacts when possible to shorten deployment time.

• Run workers separately from web traffic services.
• Set retry limits and dead letter behavior for failed jobs.
• Monitor queue depth and execution latency trends.
• Scale workers during peak windows, then reduce baseline.

Tip: Idempotent job handlers reduce duplicate side effects during retries.

Security baseline

• Use unique secrets per environment and rotate them on schedule.
• Grant API keys with least privilege and remove unused keys fast.
• Restrict dashboard access with strong passwords and MFA where available.
• Review access logs and panel activity for unexpected changes.
• Avoid committing credentials, private keys, or backup exports.

Operational baseline

• Define a deployment checklist and keep it version controlled.
• Track service health using both logs and status checks.
• Test backups and recovery paths at regular intervals.
• Document known failure patterns and internal runbooks.
• Escalate high impact incidents through support without delay.