Push Notifications for game & app developers

Push notifications built for games and apps.

DK Cloud gives indie developers and small studios the same push infrastructure used by the largest live games. Devices, schedules, campaigns and analytics in one dashboard — backed by a multi-tenant API and an SDK you control.

Multi-tenant: Organizations, projects, RBAC.
REST + SDK: TypeScript SDK, fully-documented API.
Open providers: FCM today, APNS / Web Push / Huawei ready.
Self-host friendly: One docker compose, your own Postgres + Redis.

TodayLive

Active push tokens

12 480

Delivery rate

98.6%

+0.4 pp

Invalid tokens

auto-removed

Upcoming sendsAll projects

Daily reward
Today · 19:00
Recurring
Weekend event teaser
Sat · 10:00
One-off
Streak saver
Mon · 09:30
Cron

Push that just works

Send to any device, on any platform, with retries and invalid-token handling built in.

Schedule once, forget

Daily, weekly, one-off and cron schedules per campaign. Timezone aware.

See the impact

Real delivery, failure, and engagement data — no fake dashboards.

Push notifications

One API, every provider

Send a push and DK Cloud picks the right provider, batches the request, tracks delivery, and rotates invalid tokens automatically. FCM is live, APNS and Web Push are scheduled.

Per-project provider credentials, encrypted at rest
Device rotation: when a token changes, the old one is retired safely
Backed-off retries with a hard cap on per-token attempts

Read the Push guide

9:41DK Cloud

Your daily gift is here

Open the game to claim 50 coins and a power-up.

Real mobile render — not a mock.

Integrations

Connect the tools you already use

Firebase today, more on the way. Bring your service-account JSON, validate it in one click, and start sending.

Firebase Cloud Messaging

Production-ready today.

Available

Apple Push Notification Service

Planned for the next milestones.

Roadmap

Web Push (VAPID)

Planned for the next milestones.

Roadmap

Huawei Push Kit

Planned for the next milestones.

Roadmap

Custom webhook

Planned for the next milestones.

Roadmap

Developer experience

One SDK, the same payload, every platform

JavaScript, HTML5, and Construct 3 today. Android, iOS, Unity and Godot follow the same API surface. We never expose private keys, never store your tokens, and never log secrets.

Project-scoped API keys, shown once at creation
Hashed at rest (SHA-256)
Scoped by environment: production vs sandbox

Browse the SDK reference

// Register a device with one call
await fetch('https://api.dkcloud.dev/api/v1/projects/<id>/devices', {
  method: 'POST',
  headers: {
    'authorization': 'Bearer dkp_live_…',
    'content-type': 'application/json',
  },
  body: JSON.stringify({
    externalUserId: 'player-12345',
    platform: 'ANDROID',
    pushToken: { provider: 'FCM', token: '…' },
  }),
});

Analytics

Real numbers, no vanity metrics

We never invent counts. Every chart comes from the events your project actually produced: deliveries, failures, opens, conversions. The dashboard is honest about what is implemented and what is on the roadmap.

Delivered—Available with the FCM milestone

Invalid tokens—Auto-tracked

Open rate—Roadmap

Devices—Live once a project is connected

Scheduling

Recurring pushes without cron

Pick Once, Daily, Weekly or Advanced and DK Cloud handles the rest — timezone aware, idempotent across worker restarts.

e.g. Every day at 19:00 Europe/Moscow

Once

Send at a specific date and time.

Daily

Every day at HH:mm in project timezone.

Weekly

On selected weekdays, at HH:mm.

Advanced

A 5-field cron expression, with timezone.

Security

Tenant isolation, by design

Every request carries a tenant-scoped principal. A user from Organization A asking for a project in Organization B gets 404 — not 403 — so we never leak the existence of foreign resources.

Passwords. Hashed with scrypt.
Provider credentials. AES-256-GCM with a per-record salt.
API keys. SHA-256 only — the plaintext is shown exactly once.
Tokens. Access JWTs are short-lived. Refresh tokens are rotated and stored hashed.

What we never do

Log your private keys or FCM tokens.
Return decrypted credentials in API responses.
Mix data across organizations. Ever.

REST API

Every screen, every campaign, every device — backed by a fully-typed HTTP API with OpenAPI docs.

Browse the reference

API keys

One per project, scoped by environment, with prefix-only display. Plaintext is shown once at creation.

Open API keys

SDK

JavaScript and HTML5 today, more on the way. The same payload, the same semantics, every platform.

See the SDKs

Pricing

Start free, scale when you ship

Four tiers, no per-push fees. Detailed plans, billing and usage meters land in a dedicated milestone. For now, every account starts with generous free limits.

Free

forever

Prototypes, hobby projects, games in soft-launch.

1 project
10 000 devices
1 team member
Community support

Start free

Developer

Frequently asked

Is DK Cloud production-ready?

The Push Notifications milestone is production-ready for FCM (Android). Other providers are on the roadmap and clearly labeled. The dashboard is also a work in progress — we ship final UI in waves.

Can I self-host?

Yes. A single `docker compose up` brings up Postgres, Redis, the API, the worker, and the dashboard. Production builds target `node:20-bookworm-slim`.

How do you handle token rotation?

When the SDK re-registers a device with a new push token, the previous ACTIVE token for that (device, provider) is moved to INACTIVE so future campaigns do not double-send. INVALID tokens (e.g. FCM "registration-token-not-registered") are excluded entirely.

How are provider credentials stored?

Encrypted at rest with AES-256-GCM using a per-record salt derived from a master key in your env. The plaintext is never returned in API responses.

Build something players will come back to.

Create an account, connect Firebase, and send your first push in under five minutes. No credit card required.