Real progress. Clear boundaries. No fake percentages.
Safire is in active development. This page describes the public product direction and current focus without pretending planned capabilities are already production-complete.
Turn the deep platform work into a first-class developer experience.
Safire has progressed through substantial compiler/runtime, platform, controls, Source Vault, database, web and IDE foundation work. The current public emphasis is making the day-to-day SafireIDE experience coherent, visual and commercially useful while closing the next Team Vault and full-stack slices.
Visual design surface, application-model persistence, event/context editing, inspector behaviour and developer workflow.
Windows x64 first, Safire-owned public semantics, wxWidgets implementation underneath.
Project-authoritative database design, standalone operations and SafireIDE integration.
Vault V2 foundations, remote/team model, identity, machine trust, permissions and collaboration.
Project-aware optional AI, tool permission boundaries, local/remote provider architecture and AI Pad integration.
Safire web application hosting, service integration and developer workflow.
Windows x64 first. Make it commercially useful before spreading thin.
Safire Desktop V1 uses wxWidgets as the mature native Windows implementation beneath Safire. Future platform expansion should follow a stable Safire application model rather than forcing the first release to solve every target at once.
Now
Close the Windows developer experience, deep controls, data tooling, Team Vault and AI integration.
Next
Strengthen production deployment, collaboration, web workflow and application lifecycle integration.
Future
Broader platform targets and ecosystem expansion after the V1 model is commercially solid.
“Exists” is not the same as “ready.”
Safire development separates implementation, evidence and checkpoints. Public claims should follow demonstrated behaviour rather than generated artefacts alone.
A developer can stay inside Safire for the working day.
Design
Windows, controls, data, reports and project structures.
Develop
Source, events, business logic, services and full-stack targets.
Prove
Builds, diagnostics, affected tests and QA evidence.
Deliver
Package, deploy, diagnose and maintain the resulting application.
Safire is being built in the open.
Experienced developer feedback is especially useful while the professional workflow is still being shaped.