All Services
Ongoing

Keep it running.
Keep it healthy.

Your PowerBuilder application is your business. It works. It has worked reliably for years. The goal isn't to replace it overnight ā€” it's to keep it stable, compliant, and performing while you plan your next move.

Discuss a maintenance contract ā†’ What's included ā†“
šŸ› Bug fixes ā¬†ļø PB2025 upgrades āš” Performance tuning šŸ” Security patching
Why it matters

The application works. Let's make sure it keeps working.

A PowerBuilder application left unmaintained accumulates risk silently: security debt, version incompatibilities, performance degradation, and key-person dependency ā€” all compounding until a crisis forces an emergency response.

šŸ›
Fast incident response
When something breaks in a production PB application, you need someone who can really understand the code ā€” not someone who needs three days to understand the architecture before they can touch anything.
ā¬†ļø
Version upgrades including PB2025
PB2025 brings real improvements: faster compilation, direct source control, and enhanced web service capabilities. We upgrade safely, without breaking existing functionality.
ā˜ļø
PowerServer and PowerClient

PowerClient keeps the application updated on the Windows clients. So when your users run it, the app is downloaded, configured and installed without admin rights. A strong step forward for application distribution.

PowerServer adds a very important step: it makes the application a desktop cloud one. UI is the same, but the backend is running in the infrastructure, and the client is automatically updated. If your customers are using Windows OS, this is definitely a good step forward.

āš”
Performance optimization
Legacy PB applications often retrieve full DataWindow result sets to the client before filtering. We profile bottlenecks and push filtering and caching to the right layer.
šŸ”
Security & compliance
Security patching, MFA integration, audit logging, and compliance reporting can be added to running PB applications. We know the ecosystem ā€” Visual Guard, Fidelius ISV, and the .NET interop layer.
What's included

A maintenance contract that actually covers what matters.

We structure maintenance engagements around your application's real risk profile ā€” not a generic SLA template.

01
Application Health Assessment
Every maintenance engagement starts with a structured review of your codebase, dependency inventory, version status, known issues, and risk areas. You receive a written report with a prioritized remediation plan.
Code reviewRisk inventoryRemediation plan
02
Incident Support & Bug Fixing
Agreed SLA response times for production incidents. We triage, reproduce, fix, and verify ā€” with a written root-cause analysis for every significant incident.
SLA responseRoot-cause analysisVerified fixes
03
Scheduled Improvement Sprints
Maintenance contracts include scheduled improvement sprints: version upgrades, performance tuning, and security enhancements. Planned work, delivered on a schedule you can depend on.
Version upgradesPerformance tuningScheduled delivery
04
Knowledge Documentation
Every touch of the codebase produces documentation. DataWindow changes are logged, PowerScript modifications are annotated, and architectural decisions are recorded.
Change logAnnotationArchitecture notes
05
Modernization Readiness Review
Every six months we conduct a modernization readiness review: an honest assessment of whether the application is ready for a structured migration and what the migration would involve.
Migration assessmentReadiness reportRoadmap input
FAQ

Maintenance questions we hear every time.

These questions define whether a maintenance contract is going to work for you ā€” and help you see exactly what you are signing up for.

Worried about something specific?

Tell us what keeps you up at night about your PB application. We will be direct about whether we can help.

Talk to us
Protect Your Application

Your application works. Let's keep it that way ā€” until you're ready to move.

A maintenance contract that builds toward modernization, not against it.

Discuss a maintenance contract →