> For the complete documentation index, see [llms.txt](https://docs.ternoa.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ternoa.network/learn/introduction/why-build-on-ternoa.md).

# Why build on Ternoa

**ACCESSIBILITY**

Our tech stack has been designed to cater to the needs of the greatest number of developers. Regardless of your background, or of the type of application you are looking to build, you will find a suitable dev environment to launch your project.

* On Ternoa, **new developers** making their first steps in web3 don’t need to learn how to write smart contracts to develop blockchain applications. Our javascript SDK enables this and makes Ternoa suitable for web2 audiences just entering web3, including corporations & organizations.
* **Seasoned Web3 developers** can deploy WASM smartcontracts on Ternoa Chain written in Rust, C, C++, or Typescript. And will soon be able to build EVM dapps in Solidity. Our smartcontract environments enable the most complex use cases to be built on our infrastructure, and take advantage of our built-in confidentiality features and security.

**BUILT-IN CONFIDENTIALITY FEATURES**

For developers and dapps with a need to secure, control access and transmit confidential data without relying on 3rd parties or tech platform. Ternoa natively offers privacy features through the Fortress, our decentralized key management system. Enabling developers to create and compose private yet trustless applications very easily. Builders and users can interact with the Fortress via Ternoa Chain today. The Fortress will also become accessible from Ternoa zkEVM once launched.<br>

**SECURITY**

Ternoa Chain is built with  Substrate, an open-source, thoroughly audit framework powered by state of the art Proof of Stake consensus. Our network is decentralized by hundreds of nodes and validators. And our architecture makes us natively compatible to rely upon Polkadot's network security.

Ternoa zkEVM combines zero knowledge proofs with additional TEE proofs to achieve enhanced levels of network security.

## Networks Purpose

Each of Ternoa's network serve the shared goal of making internet a more decentralized and private place , and play a specific role in this grand scheme:

<table><thead><tr><th width="162">Network</th><th>Purpose</th><th>Specifics</th></tr></thead><tbody><tr><td>Ternoa Fortress</td><td>Enable data privacy and decentralized security</td><td>The Fortress is a TEE coprocessor network, fully open source, with native key management features</td></tr><tr><td>Ternoa Chain</td><td>Facilitate the onboarding of web and web2 builders in Web3</td><td>Ternoa Chain brings in a WASM deployment environment for smartcontracts, as well as pre-coded primitives accessible with Javascript</td></tr><tr><td>Ternoa ZKEVM</td><td>Bring in enhanced TEE security to zkEVM, and make Ternoa ecosystem accessible natively from ethereum</td><td>Ternoa ZKEVM is a validium using TEE proofs to add a layer of security to zkEVM, and is fully ethereum equivalent</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.ternoa.network/learn/introduction/why-build-on-ternoa.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.