FEB CLOUD SUPPORT

Help at every step.

From choosing a product to your first deployment.

Getting started

01

Create your first cloud server

  1. Open the console and choose UHost or a lightweight cloud server.
  2. Review the region, OS image, resources and networking.
  3. Review billing before creating the resource, and keep login credentials safe.
Read full documentation
02

Choose and connect a database

  1. Choose an engine for your application’s data model and compatibility needs.
  2. Check version, size, storage and access settings in the console.
  3. Follow the product documentation to connect. Never expose credentials in public pages or code.
Read full documentation
03

Start using cloud storage

  1. Choose storage for objects, file sharing or backups.
  2. Check the region and billing items before creating resources.
  3. Set appropriate access permissions before uploading or connecting data.
Read full documentation

BILLING

Know the costs before you deploy.

Pricing calculator

Catalog prices and final bills

Published amounts come from observed console catalog cards, not account checkout prices. Configuration, tax, discounts and additional usage may affect the final amount.

Currency and exchange rates

USD is the recorded base currency. SGD uses a public Frankfurter reference rate. If the request fails, a dated fallback snapshot is used. This is not a promised payment exchange rate.

USD is the console catalog currency.

Products without a published rate card

These products link to configuration quotes; unknown charges are never treated as zero. Review your complete configuration in the console.

Frequently asked questions

How do I choose between UHost and a lightweight server?

Consider UHost when you want to plan compute, storage and networking separately. For lightweight apps, compare ULightHost bundles. Check the console for available specifications and limitations.

Are all database engines billed the same way?

Do not assume a shared rate card. Choose an engine first, then check the region, instance size, storage and applicable billing items.

How do object and file storage differ?

Consider US3 for object and content workflows, UFS for shared files, and UPFS for parallel-file workloads. Check the documentation against your application’s access pattern.

What might be billed beyond capacity?

Depending on the product, networking, requests and other resources may be billed separately. Estimates do not automatically include additional resources. Confirm the complete configuration in the console.

Are SGD amounts final checkout prices?

No. This site uses observed USD catalog prices as references and converts to SGD using a public reference rate. Taxes, account discounts and final billing are determined by the console.

Will my language and currency selections be retained?

Language is preserved in the page address. Currency is stored in this browser; clearing browser data restores the default currency.