Oninit® Nexus — Modernize The Face Of Your 4GL Without Betting The Application

You have working software written in Informix 4GL doing real work right now. The screens look dated, the people who maintain it are getting harder to recruit, and every quarter the board asks a sharper version of “what’s the plan?” The two options on the table both have problems. Rewriting the application is a multi-year programme with no guaranteed delivery date; replacing it with a packaged alternative trades known limitations for unknown ones. Doing nothing is the option that gets steadily more expensive every year you choose it.

Oninit® Nexus gives you a third option: a modern browser interface to the same 4GL application, delivered without modifying a single line of the application that already works.

The business case

• Faster delivery. The user-facing modernization story moves on a timeline measured in weeks per application, not years. The underlying 4GL is unchanged.
• Lower risk. The application is not patched, recompiled, or instrumented. The runtime is the sole authority for business logic, validation, and workflow. If the runtime worked yesterday, it works today.
• No new dependency surface. No new database, queue, cache, identity provider, or coordination service. Host accounts remain the unit of identity. Existing access controls apply unchanged.
• Audit-of-record built in. Every observed screen transition and every forwarded keystroke is recorded as append-only JSON Lines and deterministically replayable — useful in regulated environments, useful in incident review, useful in training.
• Optionality preserved. Because the platform observes rather than rewrites, the exit path is mechanical: stop the daemon and the 4GL is reachable through its terminal interface exactly as before. Vendor lock-in is bounded.
• Terminal-emulator licences off the bill. Modern browsers replace the per-seat terminal-emulator licence that’s been on the renewal line for years. A 2026 web client running on the laptop hardware you already own is the front door to the same 4GL the user has always used — no AccuTerm, Reflection, BlueZone, or equivalent renewal needed.
• Operators rebrand the UI without filing a ticket. A built-in Designer lets your operators rename fields, hide unused options, reorder menu items, and tweak layout per screen. Theme editor handles colours and fonts. All of it lives in YAML, lives outside the runtime, and is rolled back by removing the YAML block. Customisation requests that used to need a developer cycle become a five-minute operator change.

Why Oninit®

Oninit® is the team known across the Informix community as “the Down System Specialists.” When customers lose access to their data and the usual recovery routes have run out, ours are the people called in. The same engineers who built Oninit® Log Ripper, Oninit® Snooper, and the Oninit® Forensics chunk-level recovery toolkit designed and built Nexus. The architectural restraint visible in the product — narrow boundaries, runtime-neutral core, explicit out-of-scope list — is the same discipline that recovers twenty-year-old Informix instances when nothing else can.

What it removes from your risk register

• “We can’t recruit anyone willing to maintain those green-screen applications.”
• “The business has been waiting for a rewrite for years and it keeps slipping.”
• “Auditors keep asking us how we know what users did in the 4GL last quarter and we keep giving them a partial answer.”
• “We can’t trial a new vendor without exposing the 4GL to changes we cannot afford to break.”
• “We’re tired of paying for terminal-emulator licences every year just so our users can reach the 4GL.”

Next step

A 30-minute scoping call answers the obvious questions: which of your 4GL applications are best-fit for an early-access deployment, what an initial working trial looks like, and how the audit and replay outputs slot into the controls you already have in place.

Call +1-913-732-8892 (US) or +44-2081-337529 (UK), or email support.info@oninit.com.