# Ziex - Full-stack web framework for Zig!

**URL:** <https://ziggit.dev/t/ziex-full-stack-web-framework-for-zig/12848>\
**Category:** Showcase\
**Tags:** language, build-system, web\
**Created:** [November 4, 2025, 8:38pm UTC](https://ziggit.dev/t/ziex-full-stack-web-framework-for-zig/12848 "2025-11-04T20:38:08Z")\
**Posts on this page:** 11\
**Page:** 2

<div class="post-metadata">

**Author:** ![nurulhudaapon](https://ziggit.dev/user_avatar/ziggit.dev/nurulhudaapon/32/5148_2.png) [@nurulhudaapon](https://ziggit.dev/u/nurulhudaapon)\
**Post date:** [March 17, 2026, 6:35pm UTC](https://ziggit.dev/t/ziex-full-stack-web-framework-for-zig/12848/22 "2026-03-17T18:35:24Z")

</div>

Here is Server-Action Demo! But looking for feedback on the most reasonable signature.

[https://youtu.be/rLaKDNwl2FI](https://youtu.be/rLaKDNwl2FI "https://youtu.be/rLaKDNwl2FI")

_Poll ([view on site](https://ziggit.dev/t/ziex-full-stack-web-framework-for-zig/12848/22))_

Code Sample:

```zig

pub fn ProfileForm(ctx: *zx.ComponentContext) zx.Component {
    const count = ctx.state(i32, 0);

    return (
        <div @allocator={ctx.allocator} style="display: inline-flex; flex-direction: column">
            <button onclick={clientEvent} value="I'm on the client">Client Event</button>
            <button onclick={serverEvent} value="I'm on the server">Server Event</button>
            <h1>{count.get()}</h1>
            <button onclick={ctx.bind(serverIncrement)} value="I'm on the server">Increment: Server</button>
            <button onclick={ctx.bind(clientIncrement)} value="I'm on the server">Increment: Client</button>
        </div>
    );
}

fn clientEvent(ctx: zx.EventContext) void {
    const val = ctx.value() orelse "";
    std.log.info("onclick: {s}\n", .{val});
}

fn serverEvent(ctx: zx.ServerEventContext) void {
    const val = ctx.value() orelse "";
    std.log.info("onclick: {s}\n", .{val});
}

fn clientIncrement(ctx: *zx.EventContext) void {
    const val = ctx.state(i32);
    val.set(val.get() + 1);
    std.log.info("increment: {d}\n\n", .{val.get()});
}

fn serverIncrement(_: zx.ServerEventContext, sc: *zx.StateContext) void {
    const val = sc.state(i32);
    val.set(val.get() + 1);
    std.log.info("increment: {d}\n\n", .{val.get()});
}

```

---

<div class="post-metadata">

**Author:** ![kevros](https://ziggit.dev/user_avatar/ziggit.dev/kevros/32/6160_2.png) [@kevros](https://ziggit.dev/u/kevros)\
**Post date:** [March 20, 2026, 10:58pm UTC](https://ziggit.dev/t/ziex-full-stack-web-framework-for-zig/12848/23 "2026-03-20T22:58:24Z")

</div>

Just saw this and looks very interesting, it would be cool if you can swap the renderer and use it as TUI framework like is common with react, or even gui using raylib or similar

---

<div class="post-metadata">

**Author:** ![nurulhudaapon](https://ziggit.dev/user_avatar/ziggit.dev/nurulhudaapon/32/5148_2.png) [@nurulhudaapon](https://ziggit.dev/u/nurulhudaapon)\
**Post date:** [March 21, 2026, 1:55pm UTC](https://ziggit.dev/t/ziex-full-stack-web-framework-for-zig/12848/24 "2026-03-21T13:55:53Z")

</div>

Hey, thank you for taking a look! This was already in the future scope (though TUI is the last in the priority unless someone contributes) and things are designed in a way to easily and new renderer, currently there are renderer for browser (HTML Document) and renderer for server (HTML String). And there is an impressive Zig library that renders markdown on the terminal and it’s pretty good. [GitHub - JacobCrabill/zigdown: Markdown toolset in Zig ⚡ · GitHub](https://github.com/JacobCrabill/zigdown)

> <https://github.com/ziex-dev/ziex/issues/77>
>
> \- \[x\] Server - Renders HTML/MD
> 
> - \[x\] WASI Runtime 
> - \[x\] Cloudflare… - bindings
> - \[x\] Vercel - bindings
> 
> \- \[x\] Browser - Renders HTML Document
> 
> \- \[\] macOS/iOS.. - Renders Swift UI
> \- \[\] Android - Renders Native Android Elements
> \- \[\] Windows
> \- \[\] Terminal UI

---

<div class="post-metadata">

**Author:** ![nurulhudaapon](https://ziggit.dev/user_avatar/ziggit.dev/nurulhudaapon/32/5148_2.png) [@nurulhudaapon](https://ziggit.dev/u/nurulhudaapon)\
**Post date:** [March 22, 2026, 11:38pm UTC](https://ziggit.dev/t/ziex-full-stack-web-framework-for-zig/12848/25 "2026-03-22T23:38:09Z")

</div>

**Thanks all for voting! I got the API laid out and is pretty happy about how it ended up!**

[![](https://ziggit.dev/uploads/default/original/2X/d/d60d7a26e7ceb24d8bd1a177f6746b404d14930c.jpeg "Ziex Server Action and Server Event") ](https://www.youtube.com/watch?v=owDYwOH1pr4)

---

<div class="post-metadata">

**Author:** ![nurulhudaapon](https://ziggit.dev/user_avatar/ziggit.dev/nurulhudaapon/32/5148_2.png) [@nurulhudaapon](https://ziggit.dev/u/nurulhudaapon)\
**Post date:** [March 25, 2026, 7:47pm UTC](https://ziggit.dev/t/ziex-full-stack-web-framework-for-zig/12848/26 "2026-03-25T19:47:11Z")

</div>

Rebuilt `zx dev` command along with DevServer, Error Overlay, cleaner TUI for error printing and source mapping to actual .zx file!

Thanks to [https://codeberg.org/ziglang/zig/src/branch/master/lib/std/Build/WebServer.zig](https://codeberg.org/ziglang/zig/src/branch/master/lib/std/Build/WebServer.zig)!

 ![image](https://ziggit.dev/uploads/default/original/2X/5/5e43028a4baf715fb43bdab8b4e4447d9a74f9c8.webp)  
Demo: [https://youtu.be/ZQue2FvCZ3E](https://youtu.be/ZQue2FvCZ3E)

---

<div class="post-metadata">

**Author:** ![nurulhudaapon](https://ziggit.dev/user_avatar/ziggit.dev/nurulhudaapon/32/5148_2.png) [@nurulhudaapon](https://ziggit.dev/u/nurulhudaapon)\
**Post date:** [May 30, 2026, 3:00pm UTC](https://ziggit.dev/t/ziex-full-stack-web-framework-for-zig/12848/27 "2026-05-30T15:00:04Z")

</div>

Release with Zig 0.16.0 migration!

> **[Release v0.1.0-dev.1068 · ziex-dev/ziex](https://github.com/ziex-dev/ziex/releases/tag/v0.1.0-dev.1068)**
>
> This is a developer preview of Ziex; some features are still works in progress.
> Update or install the Ziex CLI using the following scripts.
> First release of Zig 0.16.0
> Installation
> Linux/macOS
> curl...

---

<div class="post-metadata">

**Author:** ![nurulhudaapon](https://ziggit.dev/user_avatar/ziggit.dev/nurulhudaapon/32/5148_2.png) [@nurulhudaapon](https://ziggit.dev/u/nurulhudaapon)\
**Post date:** [October 4, 2026, 8:38am UTC](https://ziggit.dev/t/ziex-full-stack-web-framework-for-zig/12848/28 "2026-10-04T08:38:57Z")

</div>

Ziex [v0.1.0-dev.1570](https://github.com/ziex-dev/ziex/releases/tag/v0.1.0-dev.1570) release with Zig 0.17.0 migration!

## Tooling

- `Ziex CLI`: incremental builds, improved reliability with [BSP](https://codeberg.org/ziglang/zig/issues/35538), cleaner commands, improved Windows support.
- `Ziex LSP`: tag/attribute complete and hover, improved VSCode with better LSP integration.
- `Ziex Devtools`: click/hover highlight with auto-scroll, live host data, refreshed UI.

## Core

- Richer client forms and events, optional ZXON fields, shared page/API routes, broader caching.
- WASM: blocking fetch (JSPI), optional off / optimize, stabler WASI export.
- Modularized `httpz` and added pure `std` backend with the ability to optionally use `std` backed.

## Docs & site

- Playground app mode and updated Zig/WASI compiled from official Zig repository.

---

<div class="post-metadata">

**Author:** ![nurulhudaapon](https://ziggit.dev/user_avatar/ziggit.dev/nurulhudaapon/32/5148_2.png) [@nurulhudaapon](https://ziggit.dev/u/nurulhudaapon)\
**Post date:** [October 28, 2026, 7:48pm UTC](https://ziggit.dev/t/ziex-full-stack-web-framework-for-zig/12848/29 "2026-10-28T19:48:42Z")

</div>

## Ziex 0.1.0 has arrived!

Today is our first public release and Ziex’s first birthday.

> **[Release v0.1.0 · ziex-dev/ziex](https://github.com/ziex-dev/ziex/releases/tag/v0.1.0)**
>
> Ziex 0.1.0
> Ziex is a full-stack web framework for Zig, built to be as simple as plain HTML, with the power of Zig and a declarative syntax for dynamic UI. Ziex also puts a strong focus on developer...

---

<div class="post-metadata">

**Author:** ![nurulhudaapon](https://ziggit.dev/user_avatar/ziggit.dev/nurulhudaapon/32/5148_2.png) [@nurulhudaapon](https://ziggit.dev/u/nurulhudaapon)\
**Post date:** [November 3, 2026, 2:03pm UTC](https://ziggit.dev/t/ziex-full-stack-web-framework-for-zig/12848/30 "2026-11-03T14:03:37Z")

</div>

Ziex DevTools is now on Firefox Add-Ons!

> **[Client Challenge](https://addons.mozilla.org/en-GB/firefox/addon/ziex)**

---

<div class="post-metadata">

**Author:** ![Theodore101](https://ziggit.dev/letter_avatar_proxy/v4/letter/t/a4c791/32.png) [@Theodore101](https://ziggit.dev/u/Theodore101)\
**Post date:** [November 3, 2026, 6:17pm UTC](https://ziggit.dev/t/ziex-full-stack-web-framework-for-zig/12848/31 "2026-11-03T18:17:50Z")

</div>

First and foremost, I just wanna say that I have no experience in web development (and just a little with zig), but I have a present need to do so.  
Please do not get offended with my question. I am not attempting to make a value judgment regarding Ziex. My mind would only like to conceive of the difference in approach between Ziex versus zio + dusty + zt. I had just chosen the later to start doing the web app I was required to develop, before learning about the existence of Ziex.  
Thank you sir.

---

<div class="post-metadata">

**Author:** ![nurulhudaapon](https://ziggit.dev/user_avatar/ziggit.dev/nurulhudaapon/32/5148_2.png) [@nurulhudaapon](https://ziggit.dev/u/nurulhudaapon)\
**Post date:** [November 4, 2026, 11:34am UTC](https://ziggit.dev/t/ziex-full-stack-web-framework-for-zig/12848/32 "2026-11-04T11:34:00Z")

</div>

_All types of question are fine, there is nothing to get offended about, even if you want to do value judgment that is perfectly reasonable too._

* * *

I’ll have high level fundamentals first which may sound cryptic to you but will included before I go to details:

**zt** : A templating language. (partially competing with Ziex’s .zx syntax for the server side rendering)  
**dusty** : A http server/client. (can be used with Ziex as well, by default Ziex uses [http.zig](https://github.com/karlseguin/http.zig) but provides ability to switch to std.http.Server or to Dusty if wanted, and uses JS bindings when deployed to Edge runtime - Cloudflare/Vercel/AWS Edge Lambda)  
**zio** : Something not relevant to the comparison, you can use that with Ziex as well.

**Ziex** : Full-stack web framework, includes [templating language (.zx)](https://ziex.dev/learn#writing-markup) (comparable to zt), that gets rendered in the server as well as in the browser (for interactive things). Ziex has it’s own server (by default it uses http.zig, but configurable to use std.http.Server or Dusty), but Ziex provides it’s own interface to build routes with [file system routing](https://ziex.dev/learn#pages-layouts) support.

* * *

As you can see there are many overlaps (in fact can be the same thing in case of server), however Ziex covers broader and more advance full-stack use cases, like [client side interactivity](https://ziex.dev/learn#interactivity) that you can write with Zig, [server actions](https://ziex.dev/learn#server-actions), [hydration](https://ziex.dev/examples/hydration), [streaming](https://ziex.dev/examples/streaming), [file system routing](https://ziex.dev/learn#pages-layouts), and many more. It also includes built-in [zx.db](https://ziex.dev/learn#database) and [zx.kv](https://ziex.dev/learn#kv), and Ziex provides official support to deploy to [Cloudflare Workers](https://ziex.dev/learn#deployment-cloudflare) (WASI target).

I’ll share some Ziex examples in here with you:

1. [Counter](https://ziex.dev/examples/counter)

```zig
pub fn Page(ctx: zx.PageContext) !zx.Component {
    return (
        <main @allocator={ctx.arena}>
            <Counter @client />
        </main>
    );
}
pub fn Counter(ctx: *zx.ComponentCtx(void)) zx.Component {
    const count = ctx.state(i32, 0);
    return (
        <div @allocator={ctx.allocator} class="counter">
            <button onclick={ctx.bind(increment)}>
                Click Me: {count}
            </button>
        </div>
    );
}
fn increment(e: *zx.client.Event.Stateful) void {
    const count = e.state(i32);
    count.set(count.get() + 1);
}

```

The counter logic (fn increment) runs in the browser with Zig compiled to web assembly.

1. [Routing](https://ziex.dev/learn#api-routes)

app/routes/api/route/zig → /api (GET/POST)

```zig
pub fn GET(ctx: zx.RouteContext) !void {
    try ctx.response.json(.{ .status = "ok" }, .{});
}

pub fn POST(ctx: zx.RouteContext) !void {
    const Data = struct { id: u32 };
    const data =
        try ctx.request.json(Data, .{});

    try ctx.response.json(.{
        .id = if (data) |d| d.id else 0,
        .created = true,
    }, .{});
}

```

The rest of the things, I’ll let you try in the playground, you can run Ziex in the browser and play around [here](https://ziex.dev/playground#data=eF7FVU2P2jAQ_SvTnELLJu32UlGgrFA_Vuph1bK3SJVJDLgbbMtxUCDK7-q9v6wzTmAhpF321AiRzNhvPPP8xi49pnW4ZkIGO7H0Bl6sZGZhV8AIJmKtlbF-5O2KyOu9j2QkdT6HhQQC-EIKO8CpwS1-9ODFRokEykgCPhtmACNjFGu2NOdG64AADtV3KBUkfMHy1Po952BpqmJmlelDUFZ9KCtak6LhPO7iIcIFqZOhIQpPA5llpvZX-zzrUjKb_FDaCjQwG1zmyIGzvb5jQLMlz8KUbVVug12BRDSVfnUuP7aFK7U2p0paXmAZ8UqkieHSjU0V8iW5RC6OrT0lhtvcSPBri57hyq5TmBzqHpW4TMAwHqsgZXI5ijwur-6_R974EVUjOUtaPudfc8swK2YybhF9P_t09S7yIOyaa4VN-XiqcizGDMPabK0Tdiw0nKtk2xVQsk2H2w0xWBm-wIxCrOWLWvNhyMYlZvb7F0Re9SSKzZF2hN7Q-7lYLQh5d0u4jrTD7rzL_eZWbU5a9SNJuI-N46DAfzbSiero_0Rzd-g4KI6MRm_YYxcKi_rzL8I6U9J1sx_40RpqpAGTOBW0HrWeYOmofF2dKGroDpA2AU0xTZC6npfH-U9t4WfW5DFWso89APH2GqpeDz50lVqTGlNI5JWKwr633EdQ35naKJ0FTbD98dFBUCI25_zszTOO5rm1SoKSSET8gLMpgWAuZILHWWz4mpq-qltpAPVwhTpxsBOicN02T8jRIYhfOAJ6joXT7S3gFbx5vrhc4_x_iTV9e64xPZ6tRAb4sysOLltw2Q5D_aTELqHBYETiQYv6s7nnGh4-f5wdaPhGw488HF9ndMtQfYZnSEzGg5-Zkn5QgtNfTjdL5KkHPJMqd3ldmGH1ByCpT3A).

* * *

The above was the concrete difference. Now these are my opinions:

zt can be a good option when you don’t need a full-stack framework e.g. you If your app is mostly “render HTML on the server and move on,” zt should be lighter and faster in that case. You can still choose Ziex if you like the .zx syntax over zt for the same use case. Otherwise Ziex will be something you can choose when you want the broader full-stack pieces (client interactivity in Zig, file-system routes, zx.db/zx.kv, edge/WASI deploy) etc.

[Previous page](https://ziggit.dev/t/ziex-full-stack-web-framework-for-zig/12848.md?page=1)
