Skip to main content

Pricing And Licensing

Hosanna UI is a private, commercially licensed framework written in TypeScript. This page explains how source access works, what is licensed, and how companies typically work with Tantawowa to ship apps.

Licensed Framework and Tooling​

  • Hosanna UI is licensed technology, not an open-source MIT framework.
  • Hosanna tooling, compiler, debugger, MCP workflows, and platform build systems are private Tantawowa technology.
  • Hosanna Tools installs the licensed framework and compiler versions declared by the project. Installation requires an active license key with the appropriate source and platform entitlements.
  • The standard installation places the framework in the app-local hosanna-ui/ directory from the distribution and version declared in hosanna.json.
  • Source visibility is part of the workflow: teams can inspect framework behavior, debug deeply, step through code, and maintain their app with full context.
TypeScript‑First

Your team can build apps using familiar TypeScript, state, and components while still having framework source available for debugging and day-to-day development.

Source Access​

Hosanna Tools installs full framework source for clients whose active license includes that entitlement, so teams are not working against a black box. Clients with an appropriate full-source license may also install from an authorised private GitHub repository supplied for their engagement. GitHub access and possession of the source do not grant permission to publish, redistribute, relicense, or use Hosanna outside the licensed scope.

Typical application repositories include:

  • Application source.
  • An app-local licensed framework checkout or distribution folder, with source-tree aliases pointing into it.
  • Project configuration, AppConfig, assets, and generated files.
  • Licensed tooling access for supported build and debugging workflows.

Your license entitlements determine the available source flavour, platforms, and distribution tier. npx hst license:status shows the entitlements for the active key without printing the key itself.

Install With Hosanna Tools​

Use HSC_LICENSE_KEY for local automation and CI. Avoid placing the value in a checked-in file, a command argument captured in shell history, logs, or build artifacts.

read -rsp 'Hosanna license: ' HSC_LICENSE_KEY
echo
export HSC_LICENSE_KEY

npx hst license:status
npx hst sdk:install
npx hst compiler:install

license:status must confirm an active key and the required entitlements before the licensed SDK or compiler is installed. The same key authorizes the compiler and entitled full-source SDK artifacts. CI should inject it as a masked secret only for the steps that need it.

Clients licensed for direct GitHub source access receive the approved private repository and version from Tantawowa. They may clone that source directly or configure Hosanna Tools to install from the authorised Git source. The license remains required regardless of the delivery method.

Why Teams Choose Hosanna​

  • Use existing web/connected‑device developers; no need to hire or train Roku specialists.
  • Predictable, maintainable codebases in TypeScript with modern tooling.
  • Framework source is visible in the client project for debugging, inspection, and local workflow quality.
  • Private framework and tooling licenses keep commercial rights, support expectations, and release scope clear.

Working With Tantawowa​

We build apps for clients, hand them over with documentation and source control, and teams support them in‑house using their existing developers. The codebases are designed to be transparent and maintainable because the application and framework sources are both available inside the client project.

For machine activation and compiler diagnostics, see Compiler License and Tool Setup. Commercial scope, pricing, support, redistribution, and renewal terms are contract-specific; confirm them with your Tantawowa contact rather than inferring them from the source tree.

Talk to us