PushGo

Use Message, Event, and Thing to model alerts, processes, and state.

PushGo is an open-source notification and state synchronization system. Use the public Gateway to send your first notification, or run your own Gateway to control data paths, authentication, private transports, and MCP/OAuth.

Choose Your Path

First notificationGetting StartedCreate or subscribe to a Channel, choose a Gateway, and send a working Message.Model the right dataData ModelsDecide when to use Message, Event, Thing, or a combination of them.Connect real workflowsUse CasesMap NAS alerts, CI/CD pipelines, Home Assistant, and personal automations to PushGo.Move existing scriptsMigration GuidePort ntfy, Bark, ServerChan, or webhook scripts without rebuilding everything at once.Control the GatewaySelf-HostingDeploy your own Gateway for private transports, authentication, storage, and operations.Use AI assistantsMCP ReferenceLet MCP clients send Message, manage Event, and update Thing inside authorized Channel scopes.AI agent pathAI Agent NotificationsUse MCP and OAuth so agents and chatbots can notify users, update Event, and sync Thing.HTTP entry pointNotification APISend notifications from curl, scripts, webhooks, CI/CD, NAS, and automation services.

Downloads and Endpoints

Released Components

iOS / macOS / watchOS: Download from the App Store
Android: Download APK
Gateway: Binaries and Docker images

Public Gateways

Global: https://gateway.pushgo.dev
Mainland China: https://gateway.pushgo.cn

Why PushGo

Three data models

Message handles one-off alerts, Event tracks updatable lifecycles, and Thing maintains current state for devices, services, or tasks.

Native platform delivery

Apple clients receive system notifications through APNs; Android clients can combine FCM with private transports for more flexible synchronization.

Self-hostable

Run the Gateway on your own infrastructure with persistent storage, gateway authentication, private transports, observability, and reverse proxies.

End-to-end encrypted fields

Sensitive fields can be placed in ciphertext and decrypted locally by clients while the Gateway only authenticates, relays, and dispatches.

Low migration cost

Compatibility endpoints for ntfy, Bark, and ServerChan let existing scripts keep working while you move to native PushGo models.

MCP/OAuth

The Gateway can act as an MCP HTTP Server so AI assistants can send Message, manage Event, and update Thing within authorized channel scopes.

Minimal Request

curl -X POST https://gateway.pushgo.dev/message \
  -H "Content-Type: application/json" \
  -d '{
    "channel_id": "YOUR_CHANNEL_ID",
    "password": "YOUR_CHANNEL_PASSWORD",
    "title": "Hello from PushGo",
    "body": "This is a test notification."
  }'

Continue with Getting Started to send this request with a real channel.