Stirling-PDF vs WeWeb
Side-by-side trajectory, velocity, and editorial themes.
Stirling-PDF deepens real signing and lays MCP groundwork on a fast V2 cadence
Stirling-PDF is in a heavy release cadence on its V2 line, alternating substantive minors with rapid hotfixes. The last month shipped desktop hardware-token signing (PKCS#11/smart-card and OS cert stores), a work-in-progress MCP page, JDK 25 enforcement, and large merge-memory improvements, punctuated by Postgres and desktop-signing hotfixes.
Two threads stand out: deepening real document signing (hardware tokens, shared signing, cert-store integration) and laying agent-facing groundwork via an MCP page and automation-oriented backend work. The team is also steadily reworking the V2 file-management UI that users found clunky. This is a self-hosted PDF tool maturing toward serious signing and automation use.
Expect the MCP page to move from WIP toward a usable agent interface, and the signing feature set to broaden beyond desktop-only.
WeWeb is going AI-native, letting external tools build in your project
WeWeb is pushing its visual web builder toward AI-native development. It shipped MCP support so external AI tools can understand and build directly in a WeWeb project, then followed with in-app WeWeb AI gaining planning and task tracking plus MCP quality-of-life fixes. Underneath, the core keeps getting refined — a redesigned Supabase Select, formula columns in table views, and steady editor, navigation, and publishing polish.
The arc is toward a builder where AI is a first-class way to construct apps, whether through the in-app assistant or an external tool driving the project over MCP. Recent releases pair that agentic surface with data-layer depth (Supabase, formula columns) and deployment ergonomics, suggesting WeWeb wants AI-assisted building to sit on top of a solid, data-connected foundation rather than replace it. The messaging around 'AI, visual, or both' signals a deliberately hybrid workflow.
Expect WeWeb AI and MCP to keep maturing together — richer planning, more reliable agent edits — alongside continued Supabase and data-source depth, given how these two threads dominate the recent cadence.
See more alternatives to Stirling-PDF →
See more alternatives to WeWeb →