> For the complete documentation index, see [llms.txt](https://docs.trustlesswork.com/trustless-work/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trustlesswork.com/trustless-work/oss-dapps/introduction.md).

# Introduction

We build and maintain a suite of decentralized applications that serve a dual purpose:

* **Open-source templates** you can clone, extend, and integrate.
* **Standalone tools** you can use directly to interact with Trustless Work escrows.

Each dApp showcases a different layer of the Trustless Work ecosystem—from deployment to interaction to transparency.

***

### Backoffice dApp:

**Best for:** Deploying and configuring escrows

The [Backoffice dApp:](https://dapp.trustlesswork.com) Acts as your operational dashboard. You can create new escrows, define roles, set milestones, and manage approvals.\
Depending on the wallet used to log in, users will automatically see and interact with the escrows where they hold a defined role.

***

### Demo dApp:

**Best for:** Quick integrations and SDK demos

A [lean, minimal template](https://demo.trustlesswork.com) that integrates directly with our SDK. Perfect for understanding the escrow lifecycle, testing role-based flows, and experimenting with wallet and transaction logic.\
Includes prebuilt types, hooks, and providers to help you go from zero to escrow in minutes.

***

### Escrow Viewer: 

**Best for:** Viewing and verifying on-chain escrows

A read-only interface for Testnet and Mainnet that lets anyone input a contract ID (escrow ID) and visualize its data in a structured way—roles, milestones, balances, and current status.\
It provides transparency for live escrows and serves as an open-source example of how to fetch and display escrow data from the Stellar RPC.[ LINK](https://viewer.trustlesswork.com)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.trustlesswork.com/trustless-work/oss-dapps/introduction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.