TimeZone Change Add-on for PaaS
The TimeZone Change add-on sets the operating-system timezone on every node of a MassiveGRID PaaS layer to the IANA zone you choose, so logs, cron schedules and application timestamps use your local time instead of the platform default. It applies consistently across nodes and to nodes added later by scaling.
Both buttons open the MassiveGRID PaaS dashboard with TimeZone Change pre-selected. The trial needs no credit card.
TimeZone Change Package Facts
| Attribute | Value |
|---|---|
| Package | TimeZone Change |
| Type | Add-on (attaches to an existing environment) |
| Category | Add-ons & Utilities |
| Software vendor / project | Jelastic / Virtuozzo (package) |
| Licence | Open-source add-on |
| Runtime / stack | Add-on for any container layer |
| Regions | New York, London, Frankfurt, Singapore |
| Billing | Free add-on; the host environment is billed per use from $2.46/month |
| Free trial | 14 days, no credit card |
| Uptime SLA | 100% |
What is TimeZone Change?
Containers default to UTC, which is a sound convention for servers but confusing when your team, your customers and your cron jobs think in local time. A backup scheduled for 02:00 runs at the wrong hour, log timestamps need mental arithmetic, and applications that read the system zone show times that look wrong to users.
This add-on changes the system timezone for the whole layer in one step and keeps it consistent as the layer scales. It complements, rather than replaces, application-level timezone settings: databases and frameworks that store times in UTC and convert on display can keep doing so, while cron and logs follow the zone you set.
What TimeZone Change Changes in Your Environment
Add-ons run against an environment you already have. Nothing is rebuilt, and the change can be removed from the same dashboard.
- Timezone configuration: Sets the system zone (for example Europe/London or Asia/Singapore) on every node of the layer.
- Service refresh: Restarts cron and, where needed, the application service so the change takes effect.
- Scaling support: New nodes inherit the same timezone.
- Reversible: Re-run with a different zone, or UTC, at any time.
Why Teams Choose TimeZone Change
Local-time logs and cron
Schedules and timestamps that match your office and customers.
Whole-layer consistency
Every node in a cluster keeps the same zone.
Any IANA zone
All standard timezone names supported, including daylight-saving rules.
Quick and safe
A few seconds per node, with no data changes.
How to Add TimeZone Change on MassiveGRID PaaS
Attaching the add-on takes three steps and a few minutes of waiting. No servers to provision, no configuration files to edit.
Open the installer
Click Install with free trial or Install to my account. The MassiveGRID PaaS dashboard opens with the TimeZone Change add-on pre-selected, so nothing has to be copied or pasted.
Sign up or sign in
New to the platform? Sign up for the free 14-day trial, which needs no credit card. Existing customers sign in with their usual dashboard credentials.
Pick the target environment
Choose the environment, and where relevant the node layer, that TimeZone Change should attach to, then confirm. The add-on configures itself on the running nodes without a redeploy.
Who Runs TimeZone Change on PaaS
Scheduled tasks
Backups, reports and maintenance windows expressed in local time.
Legacy applications
Software that reads the system zone and cannot be configured otherwise.
Regional deployments
Environments in Singapore or New York serving local businesses.
Why Run TimeZone Change on MassiveGRID PaaS
Built for uptime. TimeZone Change runs on MassiveGRID's high-availability platform, where every environment is covered by a 100% uptime SLA. Nodes live on redundant hosts, storage is replicated, and failed containers are restarted or migrated automatically.
Pay for what you use. Billing is hourly and per cloudlet (128 MiB RAM plus 400 MHz CPU). Vertical auto-scaling adds and removes cloudlets as load changes, so a quiet TimeZone Change environment costs a few dollars a month and a busy one grows without a migration. Full details are on the PaaS page.
Your choice of jurisdiction. Deploy in New York, London, Frankfurt or Singapore and keep data inside the region your users or regulators require. MassiveGRID is ISO 9001 certified and GDPR compliant, and has run hosting infrastructure since 2003.
No lock-in. The package is a standard Jelastic Packaging Standard (JPS) manifest. You keep root-level access to the containers, can export the manifest, and can move the workload to any other Jelastic-compatible platform or to your own servers at any time.
Related on massivegrid.com: Platform as a Service.
TimeZone Change Questions
More from the Marketplace
Packages that are often deployed alongside TimeZone Change, or that solve the same problem a different way. Browse all 84 packages.
Deploy TimeZone Change Today
Start the free 14-day trial and have TimeZone Change running in minutes. No credit card required.