> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/zentitle2-docs/developers/no-code-saas-example.md).

# No-code SaaS Example

Try Zentitle2's APIs with the no-code SaaS demo app to see how activation, deactivation, and usage-based feature limits work without writing code.

This example app allows you to quickly try and test our APIs and see how Zentitle allows you to control, manage, and track SaaS applications.

{% hint style="info" %}
This "no-code" option means that a range of people can try the platform without requiring engineering resources or skills, and it's a great way to learn how things work quickly and easily.
{% endhint %}

The other benefits are it gives context to the use of the various parts of the Zentitle2 platform and how everything works together - with our "dynamic cloud" controlling your applications in the field.

{% hint style="success" %}
Using Zentitle allows you to code to our API vs. hard coding your business models into your code. This gives you the benefits of less hassles for engineering, freedom for product managers, and the agility to change business models, pricing, and packaging in minutes vs weeks or longer.

It also allows you to use a 3rd party entitlement database that is a single source of truth.
{% endhint %}

### Time required

Doing this testing requires about an hour, including adding details to your account that will be required to drive the demo, i.e., you need to add a range of features and attributes to your product in Zentitle to connect to the app's existing features - the demo doesn't work if the features on the server side don't match those in the demo app.

Once the server side is set up, some basic data is collected from your account and edited in the sample .json file using an editor.

### Prerequisites

* <mark style="color:red;">**Reading the documentation!**</mark> Especially on [how to add a product and its associated objects.](/zentitle2-docs/ui-product-catalog/products.md)
* A trial/POC/ live account with at least the capacity for one product on the Zentitle2 UI.
* Collection of data from that account for use in the demo app.
* Downloading the demo config file that needs editing.
* A way to run the test app. e.g., an IDE like Visual Studio or a docker container.

### About the SaaS demo app

The application is a dummy application for project planning etc. On Zentitle, you can control the app and try various actions and see them working live in the demo and back on the server side, e.g., activation and deactivation of a seat, changing of the parameters and features in use in the app, based on the entitlement, consumption usage working, and limits to features (forcing upgrades to higher tiers, etc.)

{% hint style="info" %}
Testing for a few minutes and with a few changes illustrates Zentitle's powerful controls and allows you to learn how to use these useful options in your applications.
{% endhint %}

### **Getting Started**

Steps to get started:

1. Create a product/entitlement and its details on the server-side Zentitle UI.
2. Download/Unzip demo files to an easy-to-access folder.
3. Getting your API credentials.
4. Edit the .json config file.
5. Setup a demo user (for access to the app).
6. Run the app and start testing.


---

# 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.nalpeiron.com/zentitle2-docs/developers/no-code-saas-example.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.