A modern server
for Ring apps and web services.

The same service, two ways

A greeting endpoint: read a name, default it, answer politely. Below are the two versions of the very same service — line for line, same length, same order — so the only thing that differs is how the logic reads.

const express = require("express")
const app = express()
app.use(express.json())

app.post("/api/greet", (req, res) => {
    let name = req.body.name
    if (!name) { name = "stranger" }

    res.json({
        message: "Ahlan, " + name + "!"
    })
})
app.listen(8080)

RingServ([
    :port = 8080,
    :services = [
        :hello = [
            :greet = func aReq {
                cName = aReq[:payload][:name]
                if cName = "" cName = "stranger" ok
                return Reply(:ok, [
                    :message = "Ahlan, " + cName + "!" ])
            }
        ]
    ]
])

No routes to design, no verbs to choose, no body parser to remember: every service answers at /api/v1 as service.action(payload) — the same call shape RingScript pages already speak. That is the whole trick — and it holds as the application grows.

What you get

One programming model, two players

RingScript runs Ring in the browser; RingServ runs the same VM on the server — and both speak the same service.action(payload) call. Declare your services once, and move one between page and server by changing a single word. Offline-first sync included.

Trust, measured

"It runs Ring" is checked, not claimed — against the native interpreter, on three platforms, on every change. The losses are published with the wins.