Skip to main content

​
Distributed Server Marketing Integration

Distributed Server Marketing is used to sell server-based products through a Pterodactyl infrastructure. Game server rentals, ready-made server packages, resource-limited hosting, and automatically delivered server services fit this workflow. These products require more than a name and price. Node, egg, allocation, RAM, disk, CPU, ports, databases, backups, and suspension behavior can all be part of the product configuration.

​
How It Works

The admin prepares Pterodactyl, creates nodes and eggs, then enters the connection details in Zonely. A hosting product can then be published in the store. After purchase, Zonely starts the server creation or delivery flow according to the product settings. Resource limits and extra costs should be clear on the product page. Buyers should know exactly how much RAM, disk, CPU, port, database, and backup capacity they receive.
Test server products on a staging node before publishing them. Incorrect limits can waste live node capacity.

​
Preparation

Confirm that these items are ready:
  • Working Pterodactyl panel
  • At least one node
  • Required eggs
  • Allocation and port range
  • API credentials
  • Panel URL
  • Resource limits for each package
  • Pricing and extra resource costs
If nodes, eggs, or allocations are missing in Pterodactyl, creating a product in Zonely is not enough.

​
Pterodactyl Checklist

  1. Install Pterodactyl and log in as an admin.
  2. Configure the node.
  3. Add or verify the eggs you will use.
  4. Prepare allocations and port settings.
  5. Create an API key.
  6. Confirm that the panel URL is reachable externally.
Pterodactyl installation details can vary by version and hosting provider. For Zonely, the important part is that the panel is running and accessible through the API.

​
Zonely Connection Settings

  1. Open Settings > System Settings in the admin panel.
  2. Open the hosting or Pterodactyl settings area.
  3. Enter the Pterodactyl panel URL.
  4. Enter the API key.
  5. Fill in hosting logo or appearance fields.
  6. Save and test the connection.
When you rotate the API key, also check existing hosting products. If the old key is revoked, delivery may stop.

​
Create A Hosting Product

  1. Open Store Management > Hosting.
  2. Create a new server product.
  3. Enter the name, description, and price.
  4. Select the egg, node, and resource limits.
  5. Enter extra port, database, backup, and disk costs.
  6. Add visuals, colors, and background assets.
  7. Save the product.
  8. Run a test purchase and verify server creation.

​
Form Fields

FieldPurpose
Server TitleHosting package name shown in the store.
Network IPIP or network information for the server.
SubdomainOptional subdomain structure for the server.
DescriptionExplains package scope and delivery rules.
SVG IconIcon shown on the package card.
EggPterodactyl egg used to create the server.
RAMMemory assigned to the server.
DiskStorage assigned to the server.
CPUCPU usage limit.
Unit / PricePackage price or unit-based resource price.
Extra Port CostCost for additional ports.
Extra Database CostCost for additional databases.
Extra Backup CostCost for additional backups.
Suspension TimeTiming for suspension after payment or period issues.
Color PaletteVisual color used on the hosting card.
Background ImageBackground asset used in the package presentation.

​
Product Description Notes

Add these details to hosting products:
  • Included RAM and disk
  • CPU limit
  • Extra port, database, and backup costs
  • Expected delivery time
  • Where the user receives panel access
  • Suspension or deletion policy after expiration
  • Supported games or software types

​
Before Publishing

Is the Pterodactyl panel URL correct?
Does the API key work?
Does the node have enough resources and free allocations?
Does a test purchase create a server successfully?
Are resource limits and extra costs clear on the product page?

​
Common Issues

The server is not created.
Check the API key, panel URL, node status, and allocation capacity. The egg list is empty.
Check Pterodactyl eggs and API permissions. A resource error appears.
The node may not have enough RAM, disk, or allocations. Try a smaller test package. Buyers do not understand the package.
Add RAM, disk, CPU, port, database, and backup limits as a table in the description.