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.
- Client projects receive the framework sources directly in their repositories, typically as embedded submodules.
- Source visibility is part of the workflow: teams can inspect framework behavior, debug deeply, step through code, and maintain their app with full context.
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 client repositories include the framework source so teams are not working against a black box. This source access is provided under the client license for that project; it is not permission to publish, redistribute, relicense, or use Hosanna outside the licensed scope.
Typical client repositories include:
- Application source.
- Hosanna framework source as submodules or equivalent embedded sources.
- Project configuration, AppConfig, assets, and generated files.
- Licensed tooling access for supported build and debugging workflows.
Companies that hire Tantawowa to build their Hosanna apps receive project source, framework source access, and licensed tooling access needed to ship and maintain the agreed app targets.
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.