Build intelligent
    event-driven apps.

    Three commands. Three minutes.

    Same binary from your laptop to a global mesh. Powered by Pulse.

    ~/my-app
    $ pulse deploy .
    ✓ built application
    ✓ created API
    ✓ deployed
    🚀 my-app is LIVE
    Try live — 3 min Choose how you buildRead the docs

    Playground: no account, no install. Or install Pulse to self-host.

    What is Pulse?

    Pulse is a local-first runtime for building, deploying and scaling intelligent event-driven applications.

    One runtime. Three ways to build.

    Choose how you build

    Different interfaces. Same engine. All three generate and deploy to the same Pulse runtime — and they're fully interoperable.

    CLI

    For developers

    • Code-first
    • Git & CI/CD friendly
    • Scriptable
    • pulse quickstart in minutes
    Ship in 3 commands
    Desktop

    Visual drag-and-drop builder

    • No code required
    • Templates & monitoring
    • Signed installers, auto-update
    • For analysts & business users
    Download Desktop
    SDKs

    Embed in your app

    • Python
    • Java
    • Go
    • Rust
    • JavaScript
    See SDKs

    No matter how you build, your application runs on the same Pulse runtime. Start visually, continue in code, ship from CI — or the other way around.

    Five steps. One binary.

    From install to production mesh — no rewrite along the way.

    01
    Install
    $ curl -fsSL get.pulse.dev | sh
    One binary. No dependencies.
    02
    Write
    $ pulse init my-app
    Plain process(event). No boilerplate.
    03
    Deploy
    $ pulse deploy .
    API + SDK + streams generated.
    04
    Live
    🚀 my-app is LIVE
    REST, SSE, agents — instantly.
    05
    Scale
    $ pulse cluster join
    Same binary. Raft. Multi-region.

    What can I build?

    Anything event-driven. A few examples:

    AI Agents

    Autonomous workflows with tools & memory.

    Customer Support

    Triage, respond, escalate — in real time.

    Fraud Detection

    Score events as they land. Block in ms.

    Document Processing

    Extract, classify, route — pipelines built-in.

    Marketing Automation

    Event-driven journeys without a stack of SaaS.

    IoT & Telemetry

    Ingest millions of events at the edge.

    Streaming Analytics

    Materialized views, continuous aggregation.

    Browse 228 production templates

    Stop assembling infrastructure. Start shipping software.

    Everything in one runtime

    What used to require 4–5 tools — orchestrator, stream engine, materialized views, deployment platform — is now a single binary.

    Build

    Author workflows your way

    • JS, Python, Go, Rust handlers
    • YAML / JSON pipelines
    • No-code wizard
    • API extensibility
    Compute

    One stateful runtime

    • AI agents
    • Stream processing
    • Materialized views
    • Continuous aggregation
    Deploy

    From laptop to mesh

    • Embedded local mode
    • PostgreSQL backend
    • HA Raft cluster
    • Multi-region mesh

    Same binary. Four scales.

    Start local. Grow into a mesh. Never rewrite.

    Laptop
    Embedded. Zero infra.
    Production
    Same binary. Real workloads.
    HA
    Raft cluster. Resilient.
    Mesh
    Distributed. Multi-region.

    $ pulse cluster join → same code, distributed.

    Why Pulse?

    Four things that make the difference.

    No infrastructure.

    No Kafka to babysit. No Airflow. No Zookeeper. The engine is embedded.

    No lock-in.

    Self-hosted. LLM-agnostic. Your data, your infra, your models.

    No rewrites.

    Same binary from laptop to mesh. Agents, streams, views — one runtime.

    No surprises.

    Raft consensus, deterministic replay, no split-brain, no lost events.

    Wired into your existing stack

    Kafka drop-in on :9092. Push to your analytics, BI and observability. Pull from your databases and webhooks.

    KafkaPostgresS3SlackDatadogSplunkPower BISegmentAmplitudeWebhooks
    Browse all connectors
    PVSC

    Enterprise-grade AI validation

    Multi-model consensus for high-stakes AI decisions. A whole product on its own.

    Learn more

    What Pulse is not

    Not another automation tool. You write code, not clickflows. Pulse runs handlers, not glue between SaaS.
    Not a Kafka replacement to babysit. The engine is embedded — no broker to run, no Zookeeper.
    Not a SaaS you send your data to. Runs on your laptop, your VPC, your cluster. Always.
    Not a framework you have to rewrite for. Plain process(event). No decorators, no ceremony.

    Three commands. Three minutes.

    One binary. Three commands. Your first live app before your coffee is cold.

    Choose how you buildGetting started