Skip to content(if available)orjump to list(if available)

Show HN: Titan – JavaScript-first framework that compiles into a Rust server

Show HN: Titan – JavaScript-first framework that compiles into a Rust server

9 comments

·December 11, 2025

Hi HN,

I built Titan, a backend framework where you write routes and logic in JavaScript, and the CLI compiles everything into a single Rust + Axum binary using the Boa JS engine. No Node.js is required in production.

The idea is to keep JS developer experience while getting Rust performance and a self-contained deployable server.

Current features:

JS route DSL

Action system mapped to Rust

esbuild bundling

Generated Rust server with Axum

Hot-reload dev server

Single-binary output

Repo: https://github.com/ezet-galaxy/-ezetgalaxy-titan

Would love feedback on the architecture, DX, and whether this hybrid JS→Rust approach is useful.

Thanks for reading!

tigranbs

TBH, the idea seems way outdated for the current state of software engineering. The Rust compiler provides a massive benefit for AI Coding because it literally catches all the failure cases, so all AI have to do is implement the logical parts, which is usually a no-brainer for something like a Claude Code or Codex.

For example, the https://github.com/SaynaAI/sayna has been mostly Claude Code + me reviewing the stuff + some small manual touches if needed, but for the most part, I have found that Claude Code writes way more stable Rust code than JS.

It would be easier and safer to give the JS code to a translator and have it translate it into Rust, and then continue AI Dev with Rust, than to invest time in an automated compiler from JS to Rust. IMHO!

Yokohiii

Not everyone is doing the AIch

rizky05

[dead]

pavelai

While the idea is somewhat new for today's JS. And I see some benefits for this to make single-purpose servers compiled into tiny binaries. I believe it would take some time to make this popular. You should to find the niche where it's required right now. And also I would spend more time working on marketing: explainer, documentation, landing page. For example now the readme looks too ai-written

What's about code and DX: it's not a good practice to export anything using globals, this is what JS world refused to do long ago. It turns your code into a hardly debuggable mess quickly

Terretta

> Would love feedback on the … DX

Is it that the two extra characters 'an' in 'titan' are so difficult to type for the CLI, or is it just for the giggles when you 'dev'?

jitl

I guess as long as you have basically no business logic, perhaps it makes sense to orchestrate route handling in Rust?

But Boa is very very slow compared to JIT compiled JavaScript. As soon as your business logic starts trying to stand up and walk I think you’ll start hitting request latency sadness.

css_apologist

    const body = JSON.stringify({
        model: "gpt-4.1-mini",
        messages: [{ role: "user", content: "hii" }]
    });

    const r = t.fetch("https://api.openai.com/v1/chat/completions", {
        method: "POST",
        headers: {
            "Content-Type": "application/json",
            "Authorization": `Bearer ${API_KEY}`
        },
        body
    });

    const json = JSON.parse(r.body);
.. no async? i wonder how they are doing this & how they plan on more js interop

isuckatcoding

Tit? Really? Just two more letters.

Second, how does concurrency (like promises) translate to rust ?

waterTanuki

One of your merits listed is "Pure JavaScript developer experience". I don't think most devs, even JS devs would consider this a merit lol. Cool project either way.