Penton Systems / Services / Software
Software Development and automation
Software that fits the operation
Custom applications and integrations for organizations that need dependable tools more than generic platforms: written down first, tested in the lab, and shipped with monitoring and a rollback plan.
01 Capabilities
What we build
Small, maintainable systems with clear owners. We prefer extending what already works to replacing it.
- 01
Custom web applications
Secure, maintainable internal and customer-facing applications, including forms, workflows and quote handling with server-side validation.
- 02
Enterprise dashboards
Operational visibility drawn from your own systems, such as the Aurora monitoring dashboard built for our Orlando environment.
- 03
Windows and Linux integrations
Services, agents and tooling for mixed Windows Server and Debian estates, from PowerShell automation to Bash on a Raspberry Pi.
- 04
APIs, automation and monitoring
Interfaces and scheduled automation that remove manual steps, respect upstream rate limits and surface problems early.
- 05
Legacy modernization
Extending the life of working systems with careful rewrites and wrappers rather than disruptive replacement.
- 06
Custom device interfaces
Interface work for appliance-class hardware, including Sony Dash modernization and Cisco IP phone customization (prototype stage).
02 Evidence
Built here, running here
You are looking at our software. This site is engineered in-house under the direction of Scott Penton, and several of its parts are working systems you can inspect.
- A
Caching data gateway
An ASP.NET handler fetches public orbital elements and NOAA space weather on a fixed allow-list, honours provider refresh limits, persists copies to disk and serves stale data with its age when a provider refuses.
- B
Orbit propagation off the main thread
Thousands of satellites are propagated with the SGP4 model in a Web Worker once per second, so the page stays responsive.
- C
Inquiry handling
Server-side validation, rate limiting, bot screening and storage outside the web root, with a reference number for every accepted message.
- D
Authenticated fleet heartbeat
Lab machines report uptime with hashed tokens; the public view shows only coarse, safe status and never addresses or topology.
| Server | Windows Server, IIS, ASP.NET handlers in C# |
|---|---|
| Automation | PowerShell build, deploy and rollback tooling |
| Linux | Debian and Raspberry Pi OS, Bash agents |
| Browser | JavaScript modules, WebGL (Three.js), Web Workers, Canvas |
| Virtualization | Proxmox VE and Windows Hyper-V |
03 Delivery approach
Define, qualify, operate
Define
Operational requirements and constraints are written down first: who uses it, what it touches, and what happens when it fails.
Build and qualify
Releases are tested in the laboratory against defined qualification criteria before deployment.
Operate
Monitoring, documentation and a rollback plan ship with every release.
04 House rules
Boring where it matters
- 01
Secrets never live in source
Credentials stay out of repositories, runbooks and screenshots. Tokens are stored hashed where the design allows.
- 02
Rollback before rollout
Every deployment has a backup and a tested way back.
- 03
Plain logs and plain claims
Systems explain what they did, and interfaces say when data is live, cached, simulated or missing.
- 04
Handover in writing
Source, documentation and ownership terms are set in a written agreement.