Licensing
A commercial IDE with source ownership and deployable applications.
Safire licensing is built around a clear product boundary: the licensed SafireIDE provides professional productivity, while source ownership, command-line build paths and end-user runtime deployment preserve developer trust.
Licensed SafireIDE
- Visual form/window designer.
- Visual report designer direction.
- Dictionary/table designer and browse/update tooling.
- Property, event and data-binding panels.
- AI Assistant Pad, review history and controlled patch workflow.
- Templates, wizards, diagnostics and support bundle workflow.
Non-IDE and runtime boundary
- Source files remain readable and developer-owned.
- Command-line check/build path remains important.
- Runtime and end-user packages should not require the licensed IDE.
- End users receive the application and runtime components they need.
- Licensing details may vary by edition and final commercial terms.
Recommended product boundary
This table summarizes the intended boundary for review.
| Capability | Position |
|---|---|
| Safire source language | Developer-owned project source that remains readable and maintainable. |
| Compiler and CLI path | Available enough to check and build projects without forcing every task through the licensed IDE. |
| Runtime and end-user packages | Independent from the developer IDE. End users should not need SafireIDE installed. |
| SafireIDE | Licensed professional productivity product. |
| AI Assistant Pad | Licensed IDE feature for project-aware productivity, patch review, audit and diagnostics. |