Thesara - documentation

1. Introduction to Thesara

Thesara is an online marketplace for mini-applications and small games that are run directly in the browser. The idea is simple:

• users I can find and run it in a few clicks useful tools or fun mini-games
• creators can post mine very quickly mini-applications (often generated with the help of AI tools) without worrying about hosting, deployment and infrastructure

Each mini-app runs in a secure sandbox within Thesaro interface. Thesara takes care of hosting, saving balance, security and integrations, while the creator focuses exclusively on logic and UI your applications.

2. Who is Thesara for?

3. Basic terms

4. First steps - users

4.1. Arrival at Thesara

Thesara is a web platform – it is enough to open the main URL in browser. The home page shows featured and trending applications ("Trending now"), short descriptions and tags such as FREE and NEW.

As a visitor you can browse the offer and start many free applications without registration. For some more advanced functions though A user account will be required.

4.2. Registration and application

The user account enables you to:

• use of private rooms and PIN-protected content
• potential purchase of paid applications or subscriptions
• personalized features (favorites, history, NoAds status)

Registration is possible via the button Sign In in header. Supported registration methods (e.g. registration by email or via identity provider) are defined in the interface itself and can be expand over time.

4.3. Basic navigation

• On the front page you can see the highlighted applications and basic statistics (eg number of published applications).
• Clicking on the application tab opens a detailed view with description, instructions and start button (Play).
• Through the menu you can get to the FAQ, documentation and page for feedback.

5. Use of applications (players)

5.1. Launching the application

When you find an application that interests you, click on it and then on button Play. A separate page will open on which the application is loaded in a sandboxed iframe.

Most applications work immediately without any additional preparation. If the application uses rooms or PIN (e.g. for a shared list), bit ćæÅ¡ asked if you want to:

• use a common demo room
• create your own room with a PIN
• or enter the room using the PIN you received from the creator

5.2. Free and paid applications

Applications on Thesara can be:

• free – everyone can use them
• paid – access is linked to a one-time fee purchase or subscription

For paid applications, payment is processed through a secure provider payment services (eg Stripe). Card number and sensitive data do not they pass through Thesara servers.

5.3. Privacy and permissions

Mini-applications work in an isolated sandbox and do not have direct access your passwords, cookies, Thesara account or other tabs in browser. All the application sees are the data you enter yourself. and what it stores in its server-side repository.

If the application requests access to additional services (eg its own external API), the creator will clearly state this in the application description.

6. First steps - creators

6.1. Opening a creative account

The creator and the regular user use the same user account. That would published the application, first log in to Thesara, then in the main select from the menu Publish App or My Projects.

Standardni (besplatni) račun predviđen je za objavu ograničenog broja aplikacija (npr. jedne aktivne mini-aplikacije). For bigger ones broj projekata predviđen je napredni / Pro plan, opisan u zasebnom chapter of this documentation.

6.2. Supported application types

Thesara is optimized for frontend mini-applications that run in browser:

• React or other modern JS framework
• plain HTML/CSS/JS bundle
• applications generated with AI tools (LLMs)

Backend logic (if you need it) should be behind your own API or some third-party services - Thesara does not run your server-side processes, it already serves as a secure hosting and sandbox for the frontend part.

7. Publication of applications

There are two main routes to publish an application:

• Inline code – paste the source code of the component, Thesara bundles everything for you
• Upload a ZIP bundle – for more advanced scenarios, when you already have it generated dist/ or a similar folder

7.1. Publishing via inline code

1. Select in the header Publish App.
2. Select the „inline code“ mode (or a similar option in the interface).
3. Paste the code of your application - most often a React/TSX component (The AI model can generate an example adapted to Thesara).
4. Fill in the basic metadata:
   • application name
   • short and long description
   • language(s) and category
   • thumbnail / cover image (optional)
5. Select visibility (public / unlisted / private) and eventual room / storage options.
6. Save and run the post.

After that, the "build" of your application is created: Thesara adds necessary shaders, wrapper component and bundle code in one app.js which is used in the Play view.

7.2. Publishing via ZIP bundle

If you already have a ready bundle (e.g. dist/ from his own build system), you can pack it in ZIP and upload it.

1. Prepare the ZIP containing your build (HTML/CSS/JS) and the lock file (package-lock.json, pnpm-lock.yaml or similar) where applicable.
2. Select upload / bundle publication in the publication interface.
3. Fill in the metadata the same as for an inline post (title, description, thumbnail…).
4. Send the bundle for processing.

A worker process on Thesara inside the sandbox starts the installation dependencies, build, HTML sanitization (removal of illegal script tags, preparation of CSP) and preparation of everything for the Play view.

7.3. Review and approval

Every public application undergoes at least a basic review in order to reduced the risk of abuse and violation of the rules. In a typical course:

• after publication, the application receives the status "pending review"
• after automatic and/or manual verification, the application is approved and becomes visible in the application overview and search
• the creator gets a permanent Play The URL which can share with users

If the release or build is not successful, the interface displays the reason and instructions on what needs to be fixed (e.g. missing dependencies, wrong bundle structure, etc.).

7.4. Updating an existing application

When you want to upgrade the application:

• in My Projects select existing listing
• make a new post (inline or ZIP) related to the same listing
• after a successful build and approval, the new build becomes "active" for all new users

8. Rooms and server-side storage

8.1. Why rooms and storage?

Classic localStorage in the browser it only works on one device and in one browser. Thesara offers instead server-side storage and room concept:

• data can be shared between several users (e.g. members families in the same shopping list)
• the state is synchronized between multiple tabs and devices
• the in-code creator works with a simple API, while Thesara takes care of versions, conflicts and security

8.2. How the rooms look to the user

For apps that use rooms, the Play page typically offers:

• button to create a new room (PIN is generated)
• field for entering the PIN and entering the existing room
• sometimes a demo room for a quick trial without any registration

Any changes within the room (eg adding an item to the list) are immediate visible to all users connected to the same room.

8.3. Storage from the creator's perspective

The creator does not use it directly in his application

window.localStorage, but a storage helper:

• The entire saving logic goes through the Thesara API (/api/storage)
• Thesara keeps state versions and resolves conflicts when there are more the user changes the data at the same time
• all of this takes place through a sandboxed bridge – the application never does see user's JWT token

A detailed developer API for storage and rooms can be found in the technical section documentation and code examples (intended for advanced developers).

9. Monetization and payouts

9.1. Earning model for creators

Thesara supports both free and paid mini-applications. When monetization is fully active, a typical model is:

• the creator determines the price for access to his application
• Thesara processes payments through a secure payment provider (eg Stripe)
• income is divided according to a predefined ratio (e.g. 70% creator, 30% platform)

The exact ratio, currency and fee details are always clearly indicated in terms of use and creator interface.

9.2. Threshold and payout dynamics

Payments are made periodically (eg monthly), after your accumulated funds exceed the minimum threshold (for example, USD 50 or equivalent in local currency). Details about the current threshold and currency they are in the creator dashboard.

As a creator, you are responsible for the registration and payment of any fees taxes according to the laws of their country. Thesara provides an overview transaction history and statements that you can use in your records.

9.3. Subscriptions and NoAds

In addition to one-time purchases, Thesara can also offer subscriptions models (e.g. Pro plan or NoAds package) that give users:

• greater number of available applications or additional features
• exclusion of ads on the entire platform
• special profile tags and access to experimental features

Some developers can tie their apps to such plans (eg additional functions only available to Pro users).

10. Pro, NoAds and Ambassador program

10.1. Pro plan (for creators and power users)

Pro plan is designed as a package for users who intensively use Thesara - either as creators or advanced users. Typical benefits include:

• increased number of allowed active applications per account
• priority processing of builds and approvals
• possible access to advanced analytics and tools
• NoAds status included (no ads on the platform)

The specific structure of the Pro plan (price, exact benefits) of Thesara publishes at the time of the launch of the plan and keeps it up-to-date in documentation.

10.2. NoAds status

NoAds status means that in the Thesare interface no longer displays ads to the user. Status is possible can be obtained in different ways:

• through the paid NoAds package
• through the Pro / Gold / Partner plan
• as part of the reward in the Ambassador program

When NoAds is active, Thesara does not load ad scripts at all, so the experience is faster and cleaner.

10.3. Ambassador program

The Ambassador program is intended for the earliest and most active to Thesara supporters - those who promote the platform, they participate in testing and help shape it with their suggestions future features.

Typical benefits for ambassadors may include:

• permanent NoAds status and/or Pro benefits
• a special profile mark (badge) visible next to applications
• priority access to new features and beta tests
• potential referral / affiliate model (percentage of income users they bring)

Detailed rules and conditions of the Ambassador program are defined in separate document and conditions of participation. This chapter serves as an overview of the main idea of the program.

11. Security and Privacy

11.1. Sandbox and application isolation

Every mini-application on Thesara runs sandboxed iframe to the reinforced element Content Security Policy (CSP) i disabled access to sensitive resources of the parent site.

• the application does not have access to your Thesara cookies, passwords or other tabs
• all calls to Thesara API go through the parent (Play page), and not directly from the application
• JWT tokens and authentication remain isolated in the parent and never they do not send to the application sandbox

11.2. Storage security

The Storage API uses versioning (ETag) and controlled batch operations in order to prevent inconsistency and abuse. These include:

• limitation of the size of individual records
• limitation of the number of operations in one request
• rate-limiting per user and namespace

For typical applications (lists, quizzes, simple games) this one limitations are not felt in practice, but they contribute significantly system stability.

11.3. User privacy

Thesara collects only the minimum set of data required for operation account, calculation of eventual payments and improvement of the platform. A detailed list and processing rules can be found in the Privacy Policy.

Standard consent mechanisms are used for ads and third parties (cookie / consent banner). If the user refuses personalized ads or buy NoAds, ads are not displayed.

12. Frequently asked questions (summary)

The detailed FAQ is on a separate page, but here is a summary key questions and answers.

• What is Thesara? – Marketplace for mini-applications and browser games, with a focus on easy publishing (especially for AI-generated applications) and a secure sandbox for users.
• What kind of apps can I publish? – Everything belongs to the category of "lightweight" web application or game and respects the rules of use (no malicious code, illegal contents, etc.).
• How long does the post last? – Most of the time the announcement i builds are completed in a few minutes. Additional time may be required for manual inspection.
• Where are my builds stored? – On Thesara storage (local or in the cloud), with automated processes for build and serve.
• When can I withdraw the earned funds? – After what you will reach the minimum payout threshold even in regular payout cycles (eg monthly). Details can be found in the creator's dashboard.
• What is the Ambassador program? – Program for the most active supporters who help in the promotion and development of the platform and for they get special benefits (NoAds, Pro status, etc.).

13. Glossary (quick overview)