Licensing
A commercial IDE with source ownership and deployable applications.
Safire licensing is built around a clear boundary: the licensed SafireIDE provides professional productivity, while source ownership, command-line build paths and end-user deployment preserve developer trust.
Licensed SafireIDE
- Visual form/window and report design surfaces.
- Dictionary/table, class, mapper, web and help tooling.
- Project configurations, build targets, distribution and signing panels.
- Property, event and data-binding panels.
- AI Assistant Pad, review history and controlled patch workflow.
- Templates, 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.
- Target-specific distribution rules are explicit.
- Code-signing uses configured certificate references and safe password handling.
Recommended boundary
Recommended product boundary
This table summarizes the intended boundary for review.
| Area | Licensed IDE | Runtime / source path |
|---|---|---|
| Visual design | Professional productivity surface | Source remains readable and buildable |
| AI workflow | Pad, proposals, diffs, apply and audit | Source edits stay reviewable and reversible |
| Deployment | Build/package/signing tooling | End users run the app/runtime, not the IDE |
| Support | Diagnostics and bundles | Logs and artifacts help field support |
Explore Safire. Review the docs. Shape what comes next.
Safire is in active Version 1 development. The best reviewers are experienced business software developers who know the cost of fragile tools, hidden metadata and uncontrolled AI edits.