Modernize Oracle Forms. Stay in Java.

If your organization runs business-critical Oracle Forms applications and is evaluating what comes next, we’d like to talk. We’re building automation to help turn Forms applications into modern Java web apps with Vaadin, and we’re looking for teams willing to share how their systems, constraints, and modernization plans actually work.

JOIN A 30-MINUTE RESEARCH CALL

Forms still runs fine. That's not the problem.

For many teams, Oracle Forms remains stable enough to keep the business running. The harder question is what happens next: fewer developers want to work on it, the user experience feels increasingly dated, integrations get harder, and every year makes the eventual transition more expensive.

The talent is retiring, not arriving

The Forms community is aging and shrinking. PL/SQL developers are harder to hire every year, and the people who know your system are retiring.

Every alternative has a catch

A JavaScript rewrite splits your team across two stacks. APEX is solid but keeps you tied to PL/SQL and the Oracle database. Tools that re-skin Forms only buy time.

Business logic is the asset

Decades of validation rules, triggers, and workflow logic live inside your forms. Lose that in the move and you haven't migrated, you've rewritten from scratch.

A Java-native target. Automation does the heavy lifting.

We've spent 15+ years automating legacy UI migrations. Oracle Forms is the next target, and we're building it in the open, shaped by the teams who run it.

framework

Forms-shaped, but modern

Vaadin lets you build data-heavy, form-driven business apps entirely in Java: grids, validators, master-detail layouts, the patterns Forms developers already think in. No JavaScript, and no jumping between front-end and back-end stacks.

Automation

Automated transformation

We convert your .fmb structures, PL/SQL triggers, and block-level logic into clean, readable Vaadin code that your team owns and maintains. There's no black box and no proprietary runtime to stay locked into.

partnership

Shaped around your codebase

Every Forms estate is different, so you get custom transformation rules and a fixed-price fine-tuning service to reach your automation targets. The engineers behind it have run large-scale Java migrations at major enterprises.

We've automated Java UI migrations before.

Our Migration Toolkit automates Vaadin 7/8 migrations to modern Vaadin, and SwingBridge brings Java Swing apps to the web. Both are shipping products on the same automation foundation, and Oracle Forms is a separate product built on it. The figures below come from those programs, not from Forms yet. Putting real Forms numbers behind them is what these conversations are about.

85%

Of code automated in past migrations
(Vaadin 7/8, Java Swing)

60%

Lower cost than a from-scratch rewrite,
in past programs

15 y

Maintenance commitment
per Vaadin version

Trusted by enterprise Java teams

Help us build the right thing

We're talking to organizations running Oracle Forms in production today to understand the realities: the size of the estate, what's been tried, and what's blocking progress. Your input shapes our scope and priorities. No sales pitch, and no commitment.

What you get:

30 minutes with the engineer and product manager building Forms automation. Your feedback reaches them directly.
Walk us through your Forms estate, and we'll talk through what's realistic to automate.
Early access when it's ready, on terms we'll define together.