Platform/Containers/Function as a Service

Code that runs when called. Bills that don't.

Event-driven functions that scale from zero to burst and back — with no cluster to own and no invocation meter to fear.

Scale to zeroHTTP & event triggersNo invocation meter

Talk to us All Containers

Capabilities

Event-driven, operations-free

Serverless functions that respond to events so you can focus on building, not running infrastructure.

Triggers everywhere

HTTP endpoints, queues, schedules and object-storage events.

Event-driven by default →

Scale to zero

Idle functions cost nothing to run and nothing to think about.

Idle costs nothing →

Observability built in

Per-function logs, metrics and traces flow into Obersva.

Logs, metrics, traces →

Secrets & identity

Scoped secrets and service identity without hand-rolled plumbing.

No hand-rolled plumbing →

Common runtimes

Node, Python, Go, Java and .NET — plus containers for anything else.

Bring the language you have →

Private networking

Functions bind to your virtual networks with no public endpoint.

Glue code stays inside →

Versioning & rollback

Deploy new versions with instant rollback and traffic splitting.

Ship without fear →

Scheduled jobs

Cron-style schedules replace the VM that ran one script.

Retire the job server →

Concurrency controls

Caps per function protect downstream systems from stampedes.

Bursts without stampedes →

No invocation meter

Capacity is agreed in the flat fee — no per-call maths.

Costs you can predict →

Resilient by designBuilt to continue, even when hardware fails.

Predictable performanceConsistent I/O for the apps that matter.

Efficient at scaleOne flat fee. Scale without waste.

Backed by humansReal experts. Real support. Every time.

Compare the runtimes

Events, schedules, or private functions

Same runtime and the same deployment flow — the difference is what triggers your code and where it is allowed to run.

ProductionEdgeComing soon

TIER 01Most used

Event Functions

Called by your systems

HTTP and queue-triggered functions that scale from zero to burst and back, for APIs, webhooks and the glue between systems.

Best for

APIs & webhooksIntegrationsNotifications

Where it runs

Dubai AZ1Dubai AZ2RiyadhBahrainMumbaiAbu DhabiFrankfurtNairobi

Plans

FunctionsHTTP & queue triggers · 512 MB · 60sSign in →Functions Plus2 GB · 300s · concurrency controlsSign in →CustomAny memory, timeout and concurrency profileSign in →

TIER 02

Scheduled Jobs

Cron without a server

Time-triggered functions for pipeline steps, reports and housekeeping — the jobs currently living on a VM nobody wants to own.

Best for

Data pipeline stepsReports & exportsHousekeeping tasks

Where it runs

Dubai AZ1Dubai AZ2RiyadhBahrainMumbaiAbu DhabiFrankfurtNairobi

Plans

JobsCron triggers · retries · run historySign in →Jobs PlusLong-running · chained steps · alertingSign in →CustomAny schedule, chain and retry policySign in →

TIER 03

Private Functions

Inside your boundary

Functions bound to your virtual networks with no public endpoint — for code that touches regulated data or internal systems only.

Best for

Regulated processingInternal automationDatabase-adjacent logic

Where it runs

Dubai AZ1RiyadhBahrainMumbaiDubai AZ2Nairobi

Plans

PrivateVPC-bound · no public endpointSign in →Private PlusVPC-bound · dedicated capacity · no cold startSign in →CustomAny network, identity and capacity modelSign in →

Two ways to buy

Shared runtime, or reserved capacity

Neither meters invocations. The difference is how predictable you need cold starts to be.

Shared RuntimeScale to zeroFunctions run on shared capacity and cost nothing when idle — the natural home for bursty and occasional work.

No always-on server to justify

Bursts absorbed automatically

No invocation meter

Best for:Integrations and jobs

Explore Shared Runtime plans

Reserved RuntimeWarm capacityCapacity held warm for latency-sensitive functions, so the first request behaves like the thousandth.

No cold-start penalty

Predictable latency for user-facing paths

Private networking included

Best for:Customer-facing endpoints

Explore Reserved Runtime plans

Who decides, who runs it

What each group gets from FaaS

Four groups shape a cloud decision. Pick the one you belong to — the platform reads differently from each seat.

“Small ideas ship without infrastructure”

Teams deliver integrations and automation in days without a server, a cluster or a new line in the capacity plan.

GovernedSovereignPredictable

FAQs

Which languages are supported?

The common runtimes — Node.js, Python, Go, Java and .NET — plus container images where you need something specific.

Are invocations metered?

No. Capacity is agreed inside the flat fee; there is no per-call or per-GB-second meter to model.

How do we avoid cold starts?

Reserved Runtime keeps capacity warm for latency-sensitive functions; shared capacity scales to zero when idle.

Can functions reach private databases?

Yes — bind them to your virtual network and they reach managed databases privately, with no public exposure.

How do we deploy?

Through the API, CLI or your existing pipeline — the same automation path as the rest of the platform.

How is the flat fee different from public cloud pricing?

Everything inside the plan you opt for is included — no additional charge for the components that make it up. Public clouds meter each component on consumption, so the bill moves with usage. Here the plan is reserved for you and the figure you agreed is the figure you pay.

Can we drive it from Terraform and CI?

Yes. Every operation is exposed through the REST API, CLI and a maintained Terraform provider, with scoped API keys per team. If the console can do it, your pipeline can do it.

How do limits and quotas work?

Quotas are yours to shape — carve capacity per team or project and delegate inside it. Hard ceilings are a conversation, not a wall; the estate re-baselines at thresholds you approve.

Can security services be included in my plan?

Yes. Endpoint security, firewalls and WAF are scoped into the same flat fee when you add them — one figure, no separate security invoice.

Better together