Blog
Benchmarks, design decisions and how-tos: building AI agents in Synsema, and deploying them with a permission manifest, sealed secrets and an audit trail. Every post is also Markdown: add .md to its URL.
8 results for serve
A Synsema app is a website with automatic HTTPS, an installable phone app with native push, and a desktop app in its own window with your icon — from one server-rendered program and one API module. No native toolkit, no second codebase, no store required.
MCP is JSON-RPC. In Synsema the whole server is a dispatcher task and one POST route. Tools are tasks with real bodies, secrets stay sealed, and untrusted input runs under a capability ceiling.
synsema init --pwa gives any Synsema site a manifest, a service worker, icons and Web Push. It installs on Android, iOS and desktop with a home-screen icon and full screen — nothing native, no store.
A gate that waits for a real person — in the terminal, or queued behind one-time links when the program runs as a server — and denies when nobody is there. An agent cannot fake an approval.
synsema build --serve --no-console --icon turns the same server-rendered app into a double-click desktop app — a .exe with your icon on Windows, a .app on macOS, a launcher folder on Linux. The browser the user already has is the window, and the process quits when the last one closes. No Tauri, no webview, no second codebase.
cron_every takes an interval or a five-field cron expression and runs a task on its own thread, next to your routes. No crontab, no worker fleet, no message broker — and a human gate when a job needs one.
Synsema's built-in server issues and renews Let's Encrypt certificates itself. One flag turns the file you run in dev into a production HTTPS site, with HTTP/2, HSTS and www → apex.
A Synsema API is discovered by an agent in 1.37 ms, ahead of Go and Node — and the discovery documents are generated, not written.