Architecture
TermPoint is built with .NET and Avalonia UI, a cross-platform desktop framework. Schedule data is stored in a SQLite database — a single file with no server process. The .NET runtime is bundled with the application, so there is nothing extra to install or maintain.
Privacy & Data Handling
TermPoint is designed to keep all data local and minimize external communication. For a full breakdown of what's stored, what's sent over the network (crash reporting, update checks), and what TermPoint does not do, see our Privacy Statement.
Deployment & Updates
- Distributed via the Microsoft Store as an MSIX package — compatible with Intune, SCCM, and Group Policy deployment.
- Updates are delivered through the Store's standard update channel.
- Installs under standard user permissions — no admin elevation required.
Infrastructure
- Zero server infrastructure. No database server, no middleware, no web server, no license server.
- For shared use, the only requirement is read/write access to a shared folder (SMB). No special ports, services, or firewall rules beyond standard file sharing.
Security & Compatibility
- Self-contained deployment — the .NET runtime is bundled with the application, so no separate runtime installation is required.
- Runs on Windows 10 or later (64-bit). Minimal footprint: ~100 MB disk, 4 GB RAM.
- No elevated privileges needed at runtime.
Support Footprint
- No server maintenance, no patching cycles beyond the app itself, no database administration.
- If something goes wrong, uninstall and reinstall from the Store — schedule data is stored separately and is unaffected.
Source Code
The source code is open for inspection on GitHub at github.com/gschlitt/SchedulingAssistant. Subject to the conditions of the license, evaluators may download, view, compile, and analyze the source code solely for purposes of evaluating, auditing, testing, or reviewing the security, reliability, and operation of TermPoint.
Contact
[email protected]