EARLY ACCESS

STANDALONE COMPILER + RUNTIME

Dowe compiles fullstack products from .dowe source.

Write routes, views, state, and server behavior in one checked source graph. Dowe generates the platform artifacts without a Node.js application runtime.

Install Dowe

Install guide

dowe
curl -fsSL https://get.dowe.dev/install | bash

Read how it works

Outputs: server binary · SSR web · desktop · Jetpack Compose · SwiftUI

MAIN.DOWE

CHECKED
dowe
import ProductRoutes from "@/views/routes/product"
import ApiRoutes from "@/server/endpoints"

main
  views:ProductRoutes
  server port:8080
    endpoints:ApiRoutes

01

source graph

05

target families

00

Node runtime

ONE PRODUCT MODEL

Different targets. Different artifacts.

The same product graph is lowered into the output each selected platform needs.

Server

Native routing and host capabilities.

Web

Initial SSR plus route assets.

Desktop

Local web output in native windows.

Android

Generated Jetpack Compose.

iOS

Generated SwiftUI.

HOW DOWE WORKS

You define the product. Dowe handles the platform work.

Compose your own routes, layouts, pages, state, requests, and server handlers from explicit Dowe contracts.

Before generation, Dowe checks imports, props, bindings, types, routes, and server boundaries. Unsupported behavior becomes a diagnostic instead of target-specific guesswork.

Explore Views

Explore Server

PRODUCT-PAGE.DOWE

SOURCE
dowe
page ProductPage
  Section boxed:true
    Grid columns:{ xs:1 md:2 } gap:8
      Title size:"5xl"
        "A product page"
      Button href:"/docs"
        "Read the docs"

01

Check

02

Generate

03

Inspect

TARGET OUTPUT

One model does not mean one renderer.

Inspect the target model

WEB

HTML before client JavaScript.

Direct route requests return composed HTML. Navigation then loads deterministic page and layout assets.

SERVER

A native server binary.

Routing, data access, security, and host capabilities remain outside the client application.

APPS

Platform-owned UI output.

Desktop reuses web assets, while Android and iOS receive Compose and SwiftUI projects.

STRAIGHT ANSWERS

The tradeoffs are explicit.

Early access

Start small, inspect the generated output, and judge the contracts against your product.

Do I need Rust installed?

No. Dowe is distributed and run as a standalone binary. Your project is Dowe source, not a Rust workspace.

Is the web renderer custom?

Yes. Dowe generates initial SSR HTML, CSS and JavaScript route assets, plus the HTTP serving layer.

Am I limited to predefined layouts?

You compose your own routes, layouts, pages, sections, grids, state, and handlers within Dowe's checked component contracts.

TRY THE SMALLEST USEFUL THING

Start with a project you can read end to end.

Create the blank starter, run web and server, then compare its source with the artifacts under .dowe.

Install the CLI

Read the compiler source

DOCUMENTATION

Build from the layer you own.

Each path starts with the mental model, then moves into contracts, source examples, and generated behavior.

View source on GitHub

01 / PRODUCT UI

Views

Compose routes, layouts, state, interactions, forms, and portable visual components.

ROUTES · UI · STATE · INTERACTIONS

Explore Views

02 / BACKEND

Server

Define routing, data access, sessions, security, jobs, and explicit host capabilities.

ROUTES · DATA · SECURITY · RUNTIME

Explore Server

03 / TOOLING

Development

Install Dowe, run targets, test source, inspect artifacts, package, and deploy.

INSTALL · DEV · TEST · DEPLOY

Explore Development

04 / AUTOMATION

Agent workflow

Give coding agents focused guidance, validation Harnesses, diagnostics, and CodeGraph.

SKILLS · HARNESSES · DIAGNOSTICS · CODEGRAPH

Explore Agent workflow