Is DataDack Serverless ready for mission-critical production workloads?

Public Beta is for developer preview, prototyping and community benchmarking. Formal commercial SLAs and billing will be introduced at general availability, so keep critical workloads elsewhere until then.

How does 1ms billing precision work once commercial pricing launches?

Execution is metered in 1-millisecond increments rather than rounded up to 100ms blocks. A function running for 14.2ms is billed for 15ms. During the Public Beta nothing is charged.

Can I connect Public Beta functions to private DataDack VPC subnets?

Yes. Functions can attach to your private VPC subnets to reach PostgreSQL, Redis and bare-metal instances over private addresses.

What runtimes and frameworks are supported?

37 frameworks across 5 toolchains (Node, Python, Go, Ruby and Rust). See the runtimes table above for the full list.

How do I send feedback during the Public Beta?

Message the 24x7 WhatsApp NOC desk on +91 87080 45050 or use the feedback panel in the console.

Is there any credit for the rest of the platform?

Yes. Sign up through any “Claim ₹1,000 credit” button to get ₹1,000 in free credit on signup, which applies to the platform's paid products.

Sovereign MicroVM · Intel® Xeon® Platinum

Sovereign FaaS.Serverless Enginein Public Beta.

Execute code on demand with 1ms billing precision, on sovereign Indian infrastructure in Noida. Currently in Public Beta for developer preview and benchmarking: 100% Free (₹0 pricing) with no credit card required.Claim ₹1,000 in free credit on signup for the rest of the platform.

Join Free Public Beta (Console)Inspect Function Studio Compare vs AWS Lambda

NOIDA HYPERVISOR FABRIC

TIER-IV

Silicon chip on a board with gold traces radiating to four modules

100% Sovereign

Intel® Xeon® Platinum

Regionap-south-3 (Noida)

JurisdictionDPDP Act (India)

Emergency NOC Desk+91 87080 45050

WhatsApp NOC

Beta Pricing₹0 / FreeZero card needed

Billing Tick1msCeiling accuracy

Free-plan timeout30 secondsUp to 1,800s (30 mins) / Custom

Free-plan concurrency10 concurrentRaised on paid plans

Public BetaZONE: ap-south-3/NOIDA TIER-IV (CTRLS & YOTTA)/₹0 BETA PRICING/1MS BILLING TICK

MicroVM isolation

Studio preview

Integrated Function Studio& Runtime Probe

A simulated invocation against the Noida region. Output is illustrative, not live telemetry.

ap-south-3.datadack.cloud

Studio Workspace

Bundle Objects

index.mjs

package.json

index.mjs

// Illustrative handler (Node 22)
export const handler = async (event, context) => {
  const t0 = performance.now();

  return {
    statusCode: 200,
    headers: { "content-type": "application/json" },
    body: JSON.stringify({
      status: "ONLINE",
      region: "ap-south-3",
      jurisdiction: "DPDP Act 2023 / Bharat",
      latency_ms: +(performance.now() - t0).toFixed(3),
    }),
  };
};

Instance State

Status: Live (₹0 Beta)
Runtime: Node 22
Region: ap-south-3

Simulated Ingress Stream

REQ #d7a1 · 200 OK14.2ms

REQ #c9b4 · 200 OK11.8ms

REQ #f2a8 · 200 OK12.1ms

Billing precision: 1ms tick. ₹0 accrued charges during Public Beta.

One invocation, start to finish

Watch a requestbecome a bill.

01
Request reaches the edge
GET /health lands on the gateway in ap-south-3.
02
Warm or cold?
The gateway looks for a warm slot. This run finds none, so it takes the cold path.
03
MicroVM boots
An isolated microVM starts and the bundle is loaded.
04
Handler executes
Your code runs and writes its log lines.
05
Response returns
200 OK goes back through the gateway.
06
Meter settles
Execution is counted in 1ms ticks. 14.2ms bills as 15ms; nothing is charged in beta.

ap-south-3 · simulated invocationIllustrative, not live telemetry.

Client

Edge

Warm pool

MicroVM

Handler

Warm pool lookup

miss, cold path

microVM boot

200 OK · 14.2ms

> START RequestId: d7a1

> GET /health

> status: ONLINE region: ap-south-3

> END RequestId: d7a1

> REPORT duration 14.2ms billed 15ms

Billing meter15 ms billed · ₹0 charged (beta)

Architectural Engineering Standard

Deterministic Serverless by Design.

Functions run in isolated microVMs on sovereign Tier-IV infrastructure in Noida, with warm pools to absorb traffic spikes and private networking to your VPC.

Pillar 01

Say Goodbye to Cold Starts

Keep runtimes initialized with a warm pool so traffic spikes are absorbed without an initialization penalty. The pool grows with your plan.

Free: Disabled
Starter: Basic Keep-Alive
Growth: Zero-Cold-Start Pool
Pro: Dedicated Warm Containers

Pillar 02

Zero-Downtime Traffic Shift

Deploy new revisions without dropping requests. The gateway moves traffic to the new revision only after it passes its health probe.

Previous revisiondrained

New revisionhealthy, serving

Pillar 03

Private VPC Attachment

Attach functions to your DataDack VPC subnets to reach PostgreSQL, Redis and bare metal over private addresses instead of the public internet.

Private subnet routing · no public endpoint required

Pillar 04

Hardware Sandboxing

MicroVM isolation per function, running inside Tier-IV facilities in Noida that hold the certifications below.

Facility: ISO 27001 · SOC 2 Type II

Execution environments

Supported Runtimes& Frameworks

37 frameworks across 5 toolchains. Each tile shows the framework class and, where it runs a handler, its memory allocation from the platform catalogue.

Node 22

28 · Class / handler memory

React
Static output
Vite
Static output
Vue
Static output
Angular
Static output
Svelte
Static output
SolidJS
Static output
Preact
Static output
Qwik
Static output
Lit
Static output
Ember
Static output
Astro
Static output
Next.js (static export)
Static output
Docusaurus
Static output
VitePress
Static output
Starlight
Static output
Eleventy
Static output
Gatsby
Static output
Storybook
Static output
Nuxt (static)
Static output
Slidev
Static output
Next.js
SSR · 1024 MB
Remix
SSR · 1024 MB
SvelteKit
SSR · 1024 MB
Nuxt
SSR · 1024 MB
Astro (server)
SSR · 1024 MB
Qwik City
SSR · 1024 MB
Express
Server · 512 MB
NestJS
Server · 1024 MB

Python 3.12

4 · Class / handler memory

MkDocs
Static output
FastAPI
Server · 512 MB
Flask
Server · 512 MB
Django
Server · 1024 MB

Go

2 · Class / handler memory

Hugo
Static output
Go
Server · 512 MB

Ruby

1 · Class / handler memory

Jekyll
Static output

Rust

1 · Class / handler memory

Zola
Static output

Architecture audit

DataDack Public Betavs Foreign Hyperscalers

DataDack's Noida beta against AWS Lambda (Mumbai) and Google Cloud Functions. Competitor figures are published headline limits; check the provider before you rely on them.

Capability	DataDack Beta (Noida)	AWS Lambda	Google Cloud Functions	Note
Public Beta pricing	₹0.00 / 100% Free	Per request + GB-second	Per request + GB-second	No card needed during beta
Free allowance	Free plan: 360 GB-hrs / mo, 20 GB / mo transfer	1,000,000 requests / mo	2,000,000 requests / mo	Different units; not like for like
Billing granularity	1ms	1ms	100ms blocks (legacy)	Matches AWS
Max execution timeout	30 seconds (Free) to 1,800s (30 mins) / Custom	15 minutes	9 minutes (event-driven)	900 seconds (15 mins) on Pro, 1,800s (30 mins) / Custom on Enterprise
Jurisdiction	100% Indian territory (Noida)	Subject to US CLOUD Act	Subject to US CLOUD Act	DPDP Act 2023 aligned
Support escalation	WhatsApp + phone NOC desk	Support plan tiers	Support plan tiers	Direct line to the team

Legal sovereignty & MeitY alignment

Data SovereigntyGuaranteed by Indian Law

Foreign cloud providers can be compelled by extraterritorial law such as the US CLOUD Act. DataDack Serverless runs inside Noida Tier-IV facilities operated by Indian providers, under Indian jurisdiction.

DPDP Act 2023 aligned
MeitY empanelled facilities
Data stays in Indian territory
Region ap-south-3, Noida

FacilitiesTIER-IV NOIDA

Yotta NM1 Data Center: Active
CtrlS Datacenter: Active
Mumbai Data Center Region: Coming Soon