Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

indah

A Python UI framework for ephemeral cloud notebooks (Colab, Runpod). Reactive, single-port, no Node required.

Build an interactive UI from a single Python file and launch it straight from a Colab or Runpod cell. It keeps Streamlit's zero-config, single-port startup, adds the async performance of a real full-stack app, and ships its frontend pre-built so there is no Node, npm, or bun anywhere at install or runtime.

Status: early development, MVP feature-complete. The core works end to end from a clone: the reactive core, the SSE transport, async token streaming, the starter component set, and a custom-component seam. Only a 0.0.x name placeholder is on PyPI so far, so install from source for now (below). Start with docs/PLAN.md for the plan and docs/SLICES.md for what is built.

Why another one

Pain indah's answer
Streamlit reruns the whole script on every interaction Reactive signals: only the affected components update (ADR-0003)
Gradio's layout and state model get awkward past a demo Plain Python components bound to state, custom layouts
Reflex needs a Node build step that breaks in transient containers Frontend ships pre-built in the wheel; zero runtime Node (ADR-0004)
Colab's proxy does not support WebSockets SSE + HTTP POST transport that passes the proxy (ADR-0002)

How it works

flowchart LR
    subgraph Cell["Colab / Runpod cell"]
        PY["Your Python app<br/>(reactive signals)"]
    end
    subgraph ASGI["Single ASGI app, one port"]
        CORE["Reactive core<br/>signals to JSON patches"]
        API["/api: SSE + POST"]
        STATIC["Pre-built Svelte shell<br/>(static assets in the wheel)"]
    end
    Browser["Browser via platform proxy"]

    PY --> CORE --> API
    STATIC -- served over HTTP --> Browser
    API -- SSE patches --> Browser
    Browser -- POST events --> API

One port, standard HTTP plus Server-Sent Events, so it works through the network proxies of Colab and Runpod without a tunnel or a local JavaScript toolchain.

Try it

Run the built-in demo from a clone:

git clone https://github.com/leejianrong/indah && cd indah
uv sync --extra dev
make demo            # prints a URL; binds the first free port from 8000

The demo streams a mock LLM token by token into a StreamText; below it, a Select switches a live DataFrame and a colour picker (a registered custom component) two-way binds a signal - all updating over SSE, with no WebSocket and no Node. Only the components that depend on a changed value are patched; there is no full-script rerun.

Other ways to run it:

make demo-notebook   # inline in a local JupyterLab cell
make demo-docker     # in Docker on an auto-picked free port

Prefer Docker with a stable http://indah.localhost/ hostname (via a machine-wide Traefik proxy)? make demo-traefik - see docs/DEV-DOCKER.md.

Your app

An app is a tree of components bound to reactive signals. Mutate a signal and only the components that read it update - no full-script rerun:

import indah
from indah import Signal, computed, Column, Slider, Text, Session

a, b = Signal(2), Signal(3)
total = computed(lambda: f"a + b = {a.value + b.value}")

page = Column(
    children=[
        Slider(a, min=0, max=10, label="a"),
        Slider(b, min=0, max=10, label="b"),
        Text(total),
    ]
)

indah.launch(
    indah.create_app(session=Session(page))
)  # prints the URL; embeds inline in Colab/Runpod

The frontend is a pre-built Svelte shell bundled in the wheel; no Node runs at install or runtime. See docs/SLICES.md for what's next.

Components

The starter set covers a typical AI demo (input, run, streamed output):

Component Use
Text a label bound to a signal, computed, or string
Button an on_click handler (sync or async def)
Slider / TextInput / Select inputs two-way bound to a signal
Image / Plot / DataFrame display a URL/bytes, a Matplotlib figure, or a table
StreamText a container that grows token by token over SSE
Column a vertical layout container

Need something the set does not cover? Register a custom component against the public JSON protocol, no framework fork and no Node build:

import indah

indah.register_component(
    "colorpicker",
    render={
        "tag": "input",
        "attrs": {"type": "color"},
        "bind": {"value": "value"},  # element value <- signal
        "on": {"input": {"event": "input", "prop": "value"}},  # UI change -> signal
    },
)

colour = indah.Signal("#ff8800")
picker = indah.custom("colorpicker", value=colour)  # two-way, like a built-in

The pre-built shell renders it from that declarative spec at runtime. The protocol is a documented, versioned public contract: see docs/protocol.md.

Planning and design

Doc What
docs/PLAN.md Problem, solution, scope, requirements, architecture
docs/SLICES.md Vertical build increments with test plans
docs/QUESTIONS.md Decision register
docs/protocol.md The JSON UI protocol (public contract)
docs/adr/ Architecture Decision Records

Development

uv sync --extra dev
make check        # lint + fast tests (the pre-push gate)
make help         # list all targets

See AGENTS.md for repo conventions and docs/RELEASING.md for the release process.

License

Apache License 2.0.

Release files for indah 0.1.0rc1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for indah 0.1.0rc1
File Size Uploaded
indah-0.1.0rc1.tar.gz 179.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for indah 0.1.0rc1
File Interpreter ABI Platform
indah-0.1.0rc1-py3-none-any.whl Python 3 none any Details

Total release size: 233.5 kB

Release files / indah-0.1.0rc1.tar.gz

Download URL indah-0.1.0rc1.tar.gz
Size 179.3 kB
Tags Source
SHA-256 checksum
How to use checksums
ab905701b31c8056fe0a17bc0b4c0b99c761389c5da799e41b3f5452d77f1a23
BLAKE2b-256 checksum
How to use checksums
bbd7155962cc83018a9a0097b39fa3cad8a61d5fc9c4411276bcbcd26084bde5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 15, 2026.

Transparency log

Release files / indah-0.1.0rc1-py3-none-any.whl

Download URL indah-0.1.0rc1-py3-none-any.whl
Size 54.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ee9aad1988995638c19a460c340fd6efbfa6c16888de0785c32b892131e9d5f9
BLAKE2b-256 checksum
How to use checksums
f7c594ab7c2ed7e9e2a7b0ca63960c0c58ac140d5a17a8ca7bd0f127fb6cf192
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 15, 2026.

Transparency log

Release history Release notifications | RSS feed

0.2.2

2 release files

0.2.1

2 release files

0.2.0

2 release files

0.1.0

2 release files

This release

0.1.0rc1 This release

2 release files

0.0.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page