Known Limitations & Differences
This page outlines design constraints, behavioral differences, and known limitations in CloudRaya New Panel. It is intended for users who manage production workloads, automation, billing, and governance, and who need to understand what should not be expected to work the same way as in old panel.
Use this page to:
- Set clear expectations before migrating
- Identify potential operational or compliance impacts
- Plan workarounds or validation steps in advance
1. Platform-Level Constraints (By Design)
These limitations exist by design in CloudRaya New Panel.
-
Single Project Owner
Each Project supports only one Project Owner. Ownership transfers must be requested through CloudRaya Support. -
No Project-to-Project Resource Movement
Resources migrated into the Default Project cannot be moved into newly created Projects. -
Account-Level Services
Some services remain account-scoped, not project-scoped, including:- DNS Bucket
- Marketplace
- Managed Services
2. Automation & API Differences
-
No Backward Compatibility
CloudRaya New Panel APIs are not backward compatible with old panel. Scripts and integrations built for old panel may not function in new panel. -
Token and Authentication Changes
API tokens and authentication methods may differ and may require regeneration or reconfiguration. -
Response and Error Handling
Response schemas and error formats may differ from old panel and must be handled explicitly in automation and integrations.
3. Billing & Credits Limitations
-
CloudRaya Coins Restrictions
CloudRaya Coins cannot be used for:- SSL licenses
- cPanel licenses
- Managed Services
- Marketplace services
-
Minimum Top-Up Threshold
The minimum top-up amount in CloudRaya New Panel is IDR 50,000. -
Historical Billing Access
Billing history, invoices, and usage reports from Old Panel are not accessible in CloudRaya New Panel and should be exported before migration.
4. Resource Management Differences
-
Object Storage Management
CloudRaya New Panel does not provide a built-in File Explorer for StorageRaya (Object Storage). Management must be done using APIs, SDKs, CLI tools, or third-party clients. -
Kubernetes Scaling Model
CloudRaya New Panel supports autoscaling for Kubernetes worker nodes. Old Panel required manual scaling. -
Snapshot and Template Handling
VM snapshots are managed centrally through My OS Template, rather than from individual VM pages as in old panel.
5. Data & Configuration Limitations
The following items are not migrated and must be recreated manually after migration:
-
DNS Records
DNS Bucket zones remain, but DNS record sets are not carried over. -
VM Schedules
Control panel-based VM scheduling rules are not migrated. -
Historical Logs and Notifications
Action logs, notifications, and platform updates from Old Panel do not carry over to New panel.
6. Access & Governance Differences
-
Per-User Access via Projects (Recommended)
CloudRaya New Panel introduces role-based access through Project Teams. Rather than sharing the main account login, invite users to specific Projects and assign roles to control what they can access and manage. -
Audit Visibility Scope
Only actions performed in CloudRaya New Panel appear in Action Logs. Historical actions from old panel are not visible.
7. UX & Workflow Differences
-
Navigation Structure
Some menus and workflows are located in different sections compared to Old Panel. -
Project Context Requirement
Many views are project-scoped. You must select the correct Project to see the expected resources.
Support & Next Steps
If any of these limitations or differences impact your production workloads, automation, or compliance requirements, contact CloudRaya Support before migrating.
Support Email: support@wowrack.co.id
Related Guides
📄 Migration to CloudRaya New Panel – Overview