Docs

Blog

Enterprise

Pricing

About

Schedule a demo

Modern UI for SWT & Eclipse RCP — Zero Rewrites, Instant Results

Replace your legacy SWT renderer with a modern, GPU-accelerated engine. Keep your Java code. Deploy to desktop and web. Go live in one week.

GitHub

Schedule a demo

100%

OF THE CODE REMAINS
UNCHANGED

85%

LOWER COST OF MODERNIZING
A LEGACY JAVA APP

95%

FASTER DELIVERY WITH
REDUCED TEAM LOAD

0%

MAINTENANCE OVERHEAD

12X

FASTER APPLICATION
MODERNIZATION

Modernizing your App

Download our CLI tool and modernize your SWT application with zero code changes. Simply replace your JAR and see the transformation.

Download the CLI

Modernize SWT applications, Eclipse RCP projects, and other SWT-based frameworks. Automatically handles JAR replacement-the fastest way to get started.

 $ irm https://dl.equo.dev/evolve/cli/install.ps1 | iex

Selected OS: Windows (AMD64)

SHA256SUMS

Modernize your App

Run the CLI command to modernize your application. You can pass a folder, ZIP, or DMG; the CLI will automatically detect and replace the SWT JAR.

 $ equo modernize path/to/your/app

💡 Run equo modernize --help to see all available options and examples

Fine-Tune Your Experience

Control which widgets get modernized using simple JVM properties or programmatic configuration.

JVM System Properties

Quick configuration via launch flags—perfect for testing without code changes.

Programmatic Control

Full code-level control for gradual adoption—start conservative, modernize incrementally.

View Documentation on GitHub →

Why this approach matters? (rewrite vs. Equo)

A ground-up rewrite shifts teams to a new stack, new logic, and a long, risky timeline. Equo preserves your codebase and skills, so engineering time goes to features your users see–not to re-implementing what already works.

	Keep Legacy SWT	Full Rewrite (new stack)	Equo
Time to value	N/A (no UX improvement)	Years	Weeks
Opportunity cost	High	High	Low
Upfront cost	Low	Very high (hire/retrain, dual-run)	Low-Medium
Delivery risk	Low	Very high (scope creep, rewrites)	Low
UX outcome	Outdated UI/UX	Modern, eventually	Modern now (GPU, animations, theming)
Cloud / Browser	No	Yes, but only after rewrite	Yes (browser mode without rewrites)
Talent / Skills	Keep Java	New stack + retraining	Keep Java
Security & compliance	Aging surface	Re-implement controls	Enterprise modules
Maintenance	Rising costs	New long-term burden	LTS, vendor supported

The Strategic Benefits of Modernizing with SWT Evolve

Drop-In UI Modernization

Upgrade to a modern interface by simply replacing the SWT library—no code rewrites or refactors required.

Cross-Platform Deployment

Deliver your Java desktop apps on Windows, macOS, Linux, and modern web browser using the same codebase.

Built-In & Branded Themes

Apply built-in themes or unlock full brand identity customization with our enterprise option.

Free & Enterprise Option

Start with the open-source version, and scale with enterprise features when needed.

Built-in Accessibility Tools

Meet WCAG and compliance standards with included diagnostics, screen reader support, and audit tools — all available in the Enterprise edition.

Support for Modern Standards

Modern, community-driven standards with the reliability of guaranteed SLA and premium support in the Enterprise edition.

Migrate to cloud

“Web-ready” gets your SWT application running in the browser. Migration to Cloud goes further: it delivers your app as a centrally managed, secure, scalable service on AWS/Azure/GCP (or private cloud) while you keep the same Java/SWT codebase.

Why it matters?

Centralized ops, zero installs: IT ships one managed service instead of maintaining desktop installs. Updates roll out instantly to every user.

SaaS at your pace: Multi-user access, environments (dev/stage/prod), usage-based scaling, and regional deployments.

Faster releases: Plug into your CI/CD; ship UI and back-end changes with repeatable pipelines and rollbacks.

What you get? (beyond “web-ready”)

Cloud deployment model: Containerized JVM back end; SWT Evolve renders the application in the browser and connects via a secured real-time bridge.

Identity & access: SSO/OIDC/SAML, role-based access, audit logs.

Operations: Autoscaling, monitoring/metrics/logging, centralized config, backups/disaster recovery, WAF and network policy integration.

Governance: Data residency options, compliance/a11y tooling, signed artifacts and controlled release channels.

What changes vs. what stays the same?

Stays the same: Java business logic, SWT semantics (layouts/events), build tools (Maven/Gradle), tests, CI habits.

Evolves: Rendering target (browser), packaging (containers/K8s optional), identity/ops are centralized and policy-driven.

Outcome

You move from “an app installed on every desktop” to “a managed enterprise service”: easier to secure, simpler to scale, faster to update—and no code rewrite standing in the way of your roadmap.