# Zebra V2: Back in Stripes

## Why Was Zebra V1 Sunset? 

As many of you already know, we moved away from the Signal fork and decided to rebuild Zebra entirely from scratch — using only our own code.

Zebra is our flagship product, and unlike apps built on top of third-party APIs or forked logic, it’s a fully independent messaging platform. That means new features take time — but it also means **no compromises**.\
\
Learn more about current and futures features implementation here :point\_down:

{% content-ref url="/pages/pQfOT2yd8XcmXz2nQ7Q0" %}
[Zebra Features](/zkml/products/zebra/zebra-features.md)
{% endcontent-ref %}

We’re committed to delivering a smooth, reliable, and privacy-first experience.\
Thanks for sticking with us as we continue to improve it!<br>

<figure><img src="/files/icvXDc6Ls2T7DHJs1iW6" alt="" width="375"><figcaption></figcaption></figure>

## 🧱 New Zebra Tech Stack

Zebra is optimized for performance, flexibility, and full control over every layer.

**Core Technologies:**

* ⚛️ **React Native** – Cross-platform mobile interface (iOS & Android)
* ⚙️ **Go** – Core backend logic, secure and efficient
* 🧠 **Node.js** – Middleware & real-time handling
* 🌐 **Electron + TypeScript** – Desktop app (Go x Electron stack)
* 🕵️ **Anon Network (Anyone)** – IP obfuscation & private routing
* 🛡️ **Custom Infra** – No 3rd-party analytics, no tracking, ever

**Built for privacy. Built to scale. Built by&#x20;**<mark style="color:blue;">**us**</mark>**.**\ <br>

\
🦓 *“We don’t copy. We build.*\
\&#xNAN;*No backdoors. No data mining. Just full control and full transparency.*\
\&#xNAN;*Zebra is being built the hard way — the right way.”*


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://zkml.gitbook.io/zkml/products/zebra/zebra-v2-back-in-stripes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.