webforJ

Your views are Java classes, and there's no REST layer between your UI and your backend. Your Spring services go straight into the view.

@Route("/orders")
public class OrdersView extends Composite<FlexLayout> {
  private final FlexLayout self = getBoundComponent();
  private final Table<Order> table = new Table<>();

  public OrdersView(OrderService orders) {
    table.addColumn("Order", Order::number);
    table.addColumn("Customer", Order::customer);
    table.addColumn("Total", Order::total);
    table.setItems(orders.findOpen());

    Button refresh = new Button("Refresh", ButtonTheme.PRIMARY,
        e -> table.setItems(orders.findOpen()));

    self.setDirection(FlexDirection.COLUMN).add(refresh, table);
  }
}

Generate your first project in the browser with startforJ, or follow the getting started guide.

No guessing, no stale training data. One install teaches Claude Code, GitHub Copilot, Cursor, Gemini CLI and Codex the framework through the webforJ AI plugin.

claude plugin marketplace add webforj/webforj-ai
claude plugin install webforj@webforj-ai

• MCP server: live access to the webforJ docs, project scaffolding, theme generation and design token validation, so answers come from current documentation instead of training data.
• Agent Skills: step-by-step workflows for building forms, creating components, styling apps, securing routes, async work, localization and version upgrades.
• Browserless testing: views run inside plain JUnit tests, with no browser and no server, so your assistant gets a pass or a fail right after every change it makes.
• Docs that answer back: ask your question in the docs search and get a direct AI answer drawn from the docs, or open any page in ChatGPT or Claude with one click.

AI agents are starting to work inside the same apps people do. The automation layer lets an agent use your webforJ app the way a person does, with exactly the permissions of the user it works for.

• See, find, act: the agent reads the page as plain text, finds a component by its label or text, and clicks, types and chooses like a user.
• No back door: it acts through the UI, so a disabled button stays disabled and anything the user can't reach stays out of reach.
• Your agent loop: you pick the model, the prompt and when the agent runs. webforJ supplies the tools.
• MCP Apps: open a webforJ view inside an AI app's conversation, so the person and the AI work with the same live UI. Experimental.

String page = Snapshot.render(view);
var export = ComponentLocator.of(Button.class).byText("Export").locate();
UserInteraction.click(export);

craftforJ edits your app live, right in the browser, while it runs. No IDE plugin, no browser extension, no design file. Click a component, change it, watch the app update, and keep the result in your Java source.

• Click and change: select any component in the page and edit its properties while the app runs.
• Back to source: review your live edits as a diff and write the ones you keep into your Java files.
• Routes and theme: navigate every route, adjust its access rules, and tune the design tokens with an instant preview.
• An agent, not a chatbot: give the craftforJ assistant a goal, not a command. It plans, inspects the live app, writes Java, compiles it, checks the result and corrects itself across many steps in one turn. When a change restarts your app, it picks its plan up again and finishes the task. Nothing reaches your source without your approval.

Run your existing Swing, JavaFX or SWT app in the browser through the Webswing integration, then move it to webforJ one screen at a time. Your users get the web version right away, and your team rewrites at its own pace, in the language it already knows.

BASIS International has spent almost 40 years assisting organizations to modernize mission-critical systems. webforJ puts that experience behind your Java apps.

Every component comes from one design system, so screen 200 looks like screen 1. Themes, light and dark modes and design tokens are built in, and the DWC Design Kit for Figma lets designers work with the same components your developers use.

Found a bug or have an idea? Open an issue in webforj. Not sure where it belongs? Post it there and we'll route it. To contribute code, read the contributing guide.