Skip to main content

Server

An open specification for building lightweight server implementations — orchestrating domains, agents, and federated hubs that collaborate across organizations.

Philosophy

The Weblisk client framework is zero-dependency and runs anywhere. The server side follows the same principles — but as a specification, not a monolithic framework.

We define the protocols, data formats, and behaviour contracts. You implement them in whatever language or platform fits your stack. Every release ships a reference implementation so you're never guessing.

Specification-First

The server spec defines endpoints, message formats, and lifecycle hooks. Build your own implementation or use an existing one — the spec is the contract.

Language Agnostic

Go, Rust, Python, Node.js, Java — implement the spec in any language. The reference implementation is in Go, but you're not locked in.

Blueprint-Driven

Server implementations consume Blueprints — declarative definitions of APIs, data models, and workflows that generate boilerplate-free endpoints.

Agent-Ready

Server implementations natively support Weblisk Agents — autonomous services that extend your application with background processing, AI, and integrations.

Reference Implementation

The official Go implementation demonstrates the full spec in a production-ready package:

terminal 
# Install the Weblisk server (Go)
go install github.com/avaropoint/weblisk-server@latest

# Scaffold a new project from a blueprint
weblisk-server init --blueprint api-rest

# Start the dev server
weblisk-server dev

How It Fits Together

Layer What It Is Example
Client Framework Zero-dependency JS running in the browser weblisk, weblisk/signals
Server Spec Protocol and API contracts REST endpoints, WebSocket channels
Blueprints Declarative definitions of APIs, models, workflows api-rest, realtime-chat
Agents Autonomous server-side services organized under domains SEO analyzer, content analyzer, uptime checker
Domains Business function controllers that coordinate work agents SEO domain, Content domain, Health domain
Gateway Security boundary between end-user browsers and the agent network Auth, route protection, rate limiting, session lifecycle
Admin Separate admin interface — isolated network, no shared state with the gateway Agent management, domain config, observability
Hub Self-sovereign deployment with orchestrator, domains, agents, and data Your production Weblisk instance
Federation Hub-to-hub trust, data contracts, and cross-org collaboration Supply chain integration, B2B automation
Implementations Concrete server in a specific language weblisk-server (Go)
Platform Bindings Adapt the spec to specific runtimes and edge platforms Cloudflare Workers, Go, Node.js, Rust
The server specification is open and versioned. You can implement it in any language — the Go reference implementation is a starting point, not a requirement.
Specification