Platform Changes & Feature Behavior
This page provides a technical and operational view of new and updated capabilities in CloudRaya New Panel. Each feature is mapped from product changes to real-world impact, including what operators, engineers, and administrators need to know or do differently compared to old panel.
Platform Architecture Changes
Projects (Resource Organization & Team Access)
What it is
CloudRaya New Panel introduces Projects as the primary, enforced workspace for organizing cloud resources and managing team access.
Operational Impact
- Resources are scoped and managed per project by default, not just labeled or tagged
- Team access is granted at the project level, enabling controlled collaboration without sharing account credentials
- Usage, activity logs, and operational visibility can be reviewed per project for better accountability and governance
What's Different from old panel
- In old panel, Projects functioned primarily as tags for billing and reporting without enforcing access control or operational boundaries
- In new panel, Projects become logical workspaces that define both resource organization and user permissions
User Action Required
- Review and define how existing workloads should be grouped into Projects
- Invite team members to the project as needed.
Compute & Infrastructure
Virtual Machines
Status: Exists in old panel and new panel
What’s Changed
-
SSH Key Management During Provisioning
In CloudRaya New Panel, users can create or import SSH keys directly in the VM creation wizard, removing the need to switch to the SSH Key menu after deployment. -
Custom Package Creation Removed
CloudRaya New Panel no longer supports Custom Package VM specifications. New VMs must be created using the predefined packages available in the creation wizard.
The CPU, memory, and storage sliders now act as filters to find matching packages, not as tools to define fully custom specifications.
Operational Impact
- VM specifications are now standardized to predefined packages, improving consistency across environments.
- Teams can no longer fine-tune CPU, memory, and disk independently.
- SSH key setup is faster and less error-prone because keys can be applied at first access.
- Cost estimation becomes more predictable because pricing is tied directly to package tiers.
User Action Required
- Review existing provisioning and sizing guidelines that reference Custom Package workflows.
- Map common custom VM configurations from Old panel to the closest available package in New panel.
- Update internal runbooks to reflect the in-wizard SSH key creation/import flow.
Notes
- All new VMs in new panel must use predefined packages shown in the VM creation wizard.
- Existing VMs created in the old panel with custom specifications will be migrated to the closest matching predefined VM packages available in the new panel.
KubeRaya (Kubernetes)
Status: Exists in Old Panel and New panel
What’s Changed
CloudRaya New Panel introduces Auto Scale for Kubernetes worker nodes, allowing clusters to automatically adjust capacity based on defined minimum and maximum node limits. In Old panel, scaling was limited to manual node adjustments only.
Operational Impact
- Reduces manual intervention for node capacity management
- Improves responsiveness to workload demand spikes and drops
- Helps control costs by keeping scaling within defined boundaries
User Action Required
- Review and define appropriate minimum and maximum worker node limits for each cluster
- Validate autoscaling behavior in a test environment before enabling it for production
My OS Template (Snapshot Management)
What it is
A centralized management interface for VM snapshots and reusable OS templates.
Operational Impact
- Enables standardized VM builds across projects
- Speeds up recovery and scaling workflows
- Reduces configuration drift
What’s Different from old panel
- Old panel required restoring snapshots from individual VM pages
- New panel provides a unified snapshot and template management menu
User Action Required
- Identify golden images or baseline templates
- Migrate snapshot workflows into the template system
Storage & Data Services
StorageRaya (Object Storage)
Status: Exists in Old Panel and New panel
What’s Changed
The built-in File Explorer interface is discontinued in CloudRaya New Panel.
Operational Impact
- Object access should be managed through APIs, SDKs, or third-party tools
- Automation and CLI workflows become the primary management method
User Action Required
- Ensure teams have compatible S3-compatible tools or SDKs
- Update internal documentation for object storage access
CloudRaya Container Registry
What’s New
CloudRaya New Panel supports multiple registries with user-defined credentials.
Operational Impact
- Enables isolation of environments (e.g., dev, staging, production)
- Improves credential rotation and security posture
- Supports multi-team workflows
What’s Different from Old panel
- Old panel provided a single, auto-generated credential for all repositories
- New panel allows multiple registries with custom authentication
User Action Required
- Create separate registries per environment or team
- Update CI/CD pipelines with new registry credentials
Networking Services
VPC, VPN, Load Balancer, DNS Bucket
Status: Exists in Old Panel and New panel
What’s Changed
No functional changes to networking behavior or performance.
Operational Impact
- Existing network topologies continue to operate as before
- Resource management is now scoped within Projects
User Action Required
- Validate network resources are assigned to the correct Projects
Marketplace & Managed Services
Marketplace Platform Expansion
What’s New
Marketplace in CloudRaya New Panel is a unified, account-level hub for deploying platform workloads and procuring services. It supports three application types:
- Serverless Containers: one-click deployment of container-based applications (for example: WordPress, PocketBase, Moodle) as pod-based workloads
- Third-Party Applications: external managed solutions such as Zimbra and Acronis
- Licenses: procurement of services such as SSL and cPanel licenses
Operational Impact
- Centralizes application deployment and service procurement in a single entry point
- Enables rapid provisioning of platform workloads
What’s Different from Old panel
- Old panel Marketplace focused primarily on managing a limited set of third-party applications
- New panel expands Marketplace into a multi-purpose hub for container deployments, external services, and license procurement
User Action Required
- Review available Marketplace services to determine which best align with your workload
- Confirm that Marketplace transactions use Cloud Credit (real balance only) and do not support Coins
Billing & Credits
Minimum Top-Up Amount
What’s Changed
CloudRaya New Panel lowers the minimum top-up amount to IDR 50,000, compared to IDR 100,000 in old panel.
Operational Impact
- Enables smaller, more flexible balance top-ups
- Supports testing, development, and low-usage workloads with lower upfront cost
User Action Required
- No action required
- Update internal billing guidelines if your team enforces a minimum top-up policy
CloudRaya Coins
What it is
A points-based promotional credit system for voucher and coupon redemptions, separate from your real-money balance.
Operational Impact
- Separates promotional credits from cash balance for clearer financial tracking
- Improves visibility into how vouchers and campaigns are consumed across services
Limitations
CloudRaya Coins cannot be used for:
- SSL
- cPanel licenses
- Managed Services
- Marketplace applications
What’s Different from Old panel
- Old panel treated voucher and coupon credits as part of the main account balance
- New panel classifies voucher and coupon credits as Coins with restricted usage
User Action Required
- Review how your team tracks promotional credits vs real balance
- Let your team know which services are not eligible for Coin usage
Cloud Credit History
What’s New
CloudRaya New Panel provides a unified credit activity view that combines top-ups, coupon redemptions, and service usage deductions into a single, filterable timeline.
Operational Impact
- Centralizes financial activity that was previously split across Billing Detail and Invoices
- Simplifies reconciliation and usage reviews
- Improves traceability of credit movements by resource, project, and time period
What’s Different from Old panel
- Old panel displayed usage details and top-up/invoice history in separate menus
- New panel consolidates all credit additions and deductions into Cloud Credit History with filtering by type, resource, and date
User Action Required
- No action required
- Update internal finance or reporting workflows to reference Cloud Credit History as the primary source for credit movement tracking
Monthly Usage History
What’s Changed
Previously labeled as “History” in old panel, now expanded to provide clearer monthly breakdowns.
Operational Impact
- Supports forecasting and budget reviews
Security & Observability
Action Logs (Audit Trail)
What it is
A centralized audit log capturing user actions across projects and resources.
Operational Impact
- Supports compliance and incident response
- Improves troubleshooting and post-mortem analysis
What’s Different from Old panel
- Old panel did not provide a platform-wide audit trail
User Action Required
- Define log retention policies
- Integrate logs into internal audit workflows
Platform Integration & Automation
API & Automation Users
What’s Changed
CloudRaya New Panel introduces a new API model with differences in endpoint structure, authentication flow, and response formats. Automation and integrations built for Old panel may not be compatible with New panel without updates.
Operational Impact
- Existing scripts, CI/CD pipelines, and third-party integrations may stop working or return unexpected responses
- API authentication and token handling may need to be reconfigured
- Infrastructure-as-code and monitoring tools may require validation and updates
What’s Different from Old panel
- Old and New panel use different API endpoints and authentication mechanisms
- New panel introduces updated response schemas and error handling behavior
Recommended Action
- If your environment heavily relies on CloudRaya APIs, we recommend postponing migration until the CloudRaya New Panel API documentation is available
- Pause automation and scheduled jobs during the migration window
- Monitor CloudRaya platform updates for the release of New panel API documentation
- Validate all scripts and integrations in a controlled environment before re-enabling production workflows
Full Feature Comparison
For a complete, side-by-side view of how each feature behaves in old panel and new panel, including minor and major changes, see:
CloudRaya Old vs New Feature Comparison
Summary
CloudRaya New Panel is a platform maturity upgrade, not a replatform.
It introduces:
- Stronger identity and governance
- Clearer cost and usage visibility
- Standardized application and deployment workflows
- Improved auditability and automation readiness
While maintaining the same underlying infrastructure services and operating model you already use.