Local / City

How do enterprises deploy an AI cloud in Perth with data residency?

An AI cloud in Perth lets mining and resources teams use frontier models through an OpenAI-compatible API while prompts, embeddings and logs stay in a documented region. Plugsky runs region-locked data planes - APAC (Singapore) is the nearest documented option for Australia - with 30+ models, flat self-serve plans and VPC, on-prem or air-gapped deployment. Change the base URL, keep your SDK, and start free.

Key facts

API compatibilityOpenAI-compatible /v1/chat/completions - change base_url and model name
Models30+ models behind one API, from free tiers to frontier reasoning
Nearest data planeAPAC (Singapore); region-locked, so prompts, completions, embeddings and logs stay in-region
DeploymentPlugsky cloud, your VPC, on-prem or air-gapped
RAG and embeddingsEmbeddings and retrieval are live for private document search
Pricing modelFlat monthly self-serve plans; no per-token billing on self-serve
Free tierFree plan with 2 free AI models (plugsky-micro, plugsky-lite), no card

TL;DR

  • Pin the APAC (Singapore) plane so prompts, completions, embeddings and logs stay in one jurisdiction.
  • An OpenAI-compatible API means a base-URL change, not a rewrite, for Perth teams.
  • One API covers small pilots and frontier reasoning, so models can change without a migration.
  • Deploy in a VPC, on-prem or air-gapped when Australian privacy law obligations or internal policy require it.
  • Evaluate on the free plan or the 14-day full-access trial before committing.

How it works, step by step

  1. Map which Perth workloads touch personal or regulated data, and classify each one.
  2. Choose a data plane; for Australia the nearest documented option is APAC (Singapore).
  3. Create a Plugsky account and API key on the free plan (two models, no card), or use the 14-day full-access trial.
  4. Change base_url to api.plugsky.com, map model names, and run your existing tests and evals.
  5. Measure latency from your Perth network and set timeouts and retries for your workload.
  6. Add scoped keys and logging, then decide whether a VPC, on-prem or air-gapped deployment is required.
1Map which Perthworkloads touchpersonal or2Choose a dataplane; forAustralia the3Create a Plugskyaccount and API keyon the free plan4Change base_url toapi.plugsky.com,map model names,5Measure latencyfrom your Perthnetwork and set6Add scoped keys andlogging, thendecide whether a

Original data

OpenAI-compatiAPI compatibility30+ models behModelsFree plan withFree tierSource: Plugsky facts table · updated 2026-09-26

Try it yourself

Open the API latency tester →

Why Perth teams choose where AI runs

Perth is Western Australia's capital and a base for mining, energy, engineering and remote-operations technology. AI work here often supports asset-heavy operations, safety documentation and logistics across very large distances. Australian privacy law applies, and Perth's subsea links to Southeast Asia shape which regional data plane makes sense.

Production workloads in Perth usually sit in mining and resources, energy and engineering and remote operations and logistics. Australia's Privacy Act and the Australian Privacy Principles apply to personal information. That turns region choice into an architecture decision: inference, embeddings, retrieval and logs should be pinned to the same place, and the choice should be provable with documentation rather than assumed from a vendor page.

How an AI cloud deployment in Perth works on Plugsky

Plugsky exposes an OpenAI-compatible /v1/chat/completions endpoint, so migration is a base URL change plus model mapping: your SDK, streaming, function calling and JSON mode keep working. The catalogue holds 30+ models, from the free plugsky-micro and plugsky-lite tiers to frontier reasoning models. Measure latency from site networks, not just the office.

Plugsky supports region-locked data planes; see /data-residency. For Australia, the nearest documented plane is APAC (Singapore), and prompts, completions, embeddings and logs stay in-region by architecture. Enterprise adds customer-managed keys, zero-knowledge mode and right-to-audit clauses; where in-country processing is mandatory, the same API runs in your VPC, on-prem or air-gapped.

Latency, failover and multi-region design

Perth's subsea routes to Singapore make the APAC plane a natural fit; for many workloads it is the lowest-latency documented option rather than a compromise.

Remote operations need rehearsed continuity: same-region restore, exported logs, and an explicit rule on whether Australian residency allows regional failover.

A rollout plan that fits Perth

Start with one mining and resources workflow and a fifty-question evaluation set drawn from real cases. Pin the APAC (Singapore) plane while you evaluate on the free plan (plugsky-micro and plugsky-lite, no card), or use the 14-day full-access trial for larger models, then measure answer quality and round-trip time from your own network. Before production, settle scoped keys with rotation, log retention, a model allow-list tied to evaluations, and a deployment choice that follows from Australian privacy law obligations.

Honest comparison

CapabilityPlugskySingle-endpoint AI APIBuilding in-house
Region optionsEU, GCC, APAC and US planes; Riyadh on EnterpriseUsually one global endpointYou operate every region
Residency enforcementRegion-locked by architectureOften contractual onlyYou build the controls
Migration effortBase URL plus model mappingVendor-specific SDKFull rewrite
Model choice30+ models behind one APISingle-vendor catalogueYou host each model
Pricing modelFlat monthly self-serve, no per-token billingPer-token meteringGPU plus operations cost
Endpoint roadmapAudio, images, moderation, files, batch and fine-tuning coming soonVaries by vendorSeparate pipelines to maintain

Frequently asked questions

Which region should a Perth workload use?

The nearest documented plane for Australia is APAC (Singapore); verify current availability at /data-residency before pinning production.

Does Plugsky have a data center in Perth?

Plugsky does not publish city-level data center locations. Region availability is listed at /data-residency, and enterprise teams can deploy in their own VPC, on-prem or air-gapped environment.

Is there a free plan?

Yes - the free plan includes two free AI models (plugsky-micro and plugsky-lite) with no credit card required.

How does pricing work?

Self-serve plans are flat monthly with unlimited fair-use usage and no per-token billing; see the live pricing page for current plans.

Can we keep our existing OpenAI SDK code?

Yes. Change the base URL to api.plugsky.com and map model names; streaming, function calling and JSON mode continue to work.

Can data stay inside our own network?

Yes. VPC, on-prem and air-gapped deployments are available, with customer-managed keys and audit-log export on Enterprise.

Is a trial available?

Yes - a 14-day full-access trial is available alongside the free plan for evaluation.