Compose the interface visually, bind state and native capabilities, preview the behavior, and export a complete Tauri 2 project for React, Vue, or Svelte.
Actual running product, captured from the browser edition.
From pane to package
Paneweaver connects visual composition, application behavior, native permissions, generated source, and local development in one deliberate flow.
Build pages from layout, content, control, data, and media components.
Connect typed state, form values, lists, tables, visibility, and media.
Add ordered actions and expose only the native capabilities the app needs.
Exercise state, navigation, action chains, and browser-safe native adapters.
Take a complete React, Vue, or Svelte Tauri 2 source tree with you.
The working product
Switch between the main Paneweaver workflows below. Every image was captured from the running application, not rebuilt as a marketing mockup.
Visual composition
Place and nest 21 visual components, move through the layer tree, manage pages, and tune granular properties without hiding the resulting source model.
Start where the project is
Paneweaver does not require a greenfield rewrite. Choose the ownership model that matches the work.
Create a framework-neutral project, choose React, Vue, or Svelte, and compose the application in Paneweaver.
Begin with a blank desktop app, showcase, focus dashboard, settings utility, or quick launcher.
Browse included templatesAnalyze a web project without installing dependencies or running package scripts, then wrap compatible source with Tauri 2.
Framework choice is a project decision
Paneweaver stores pages, components, state, actions, assets, and native capabilities in a framework-neutral project model. The selected adapter controls the generated frontend source.
Components, hooks, and TypeScript source.
src/App.tsx
Single-file components and Composition API.
src/App.vue
Typed Svelte components and reactive state.
src/App.svelte
Desktop-native, deliberately
Paneweaver turns low-level Tauri plugins and capability manifests into understandable actions, scopes, dependencies, and generated Rust initialization.
Least privilege by design. The generated capability file reflects only the native functionality enabled by the project.
No runtime lock-in
Export a normal Tauri 2 repository with framework source, Rust configuration, capability manifests, project assets, CI, and a user-owned extension point.
src/App.tsxFramework sourcesrc/paneweaver/runtime.tsState and action runtimesrc/custom/actions.tsYour extension pointsrc-tauri/capabilities/default.jsonNative permissions.github/workflows/release.ymlCross-OS release workflow
Product status
The working edition is intentionally local-first. Cloud synchronization and collaboration belong to the paid private beta and are shown separately below.
Included templates
Every built-in starting point was authored for Paneweaver and carries explicit provenance in the generated project.
A clean window and empty page root for complete control.
A multi-page example with state, data, media, native actions, and reusable blocks.
A calm navigation shell, daily focus panel, and working metrics.
A practical preferences application with sidebar navigation and forms.
A compact borderless command launcher with search and result states.
Launch pricing
The Local edition is the working product today. Paid plans below are launch targets for the private beta and will activate as their cloud capabilities ship.
Learn, prototype, and build on your own machine.
$0forever
At cloud beta: 2 synced projects, 2 GB, and 3 trial build credits.
Serious individual builders who want sync and source control.
$24/ month
Professional developers preparing products to ship.
$49/ month
Teams that share architecture, source, and releases.
$69/ editor / month
Organizations that need policy, identity, and control.
$119/ editor / month
Custom control-plane options, data residency, HSM/signing integrations, legal and security review, SLA, and volume pricing.
Start a conversation| Capability | Local | Studio | Pro | Team | Business |
|---|---|---|---|---|---|
| Local projects and source export | Unlimited | Included | Included | Included | Included |
| Cloud projects | 2 at beta | Unlimited | Unlimited | Unlimited | Unlimited |
| Storage | 2 GB at beta | 25 GB | 25 GB | Pooled | Custom |
| GitHub connection | — | Repository + diff | Repository + diff | Branches + PRs | Policy governed |
| Private components and templates | Local personal | Personal | Personal | Shared team | Private repositories |
| Build credits / month | 3 trial | 20 | 60 | 75 / editor | Custom |
| Signing and releases | Local/manual | — | Included | Included | Governed |
| Collaboration | — | — | — | Realtime + review | Realtime + SSO |
| Audit and policy | — | — | Dependency reports | Audit history | Advanced policy + export |
Failed jobs caused by Paneweaver infrastructure are refunded. Proposed overage pack: 25 credits for $15.
Questions, answered plainly
Desktop engineering still has constraints. Paneweaver makes them visible, structured, and easier to manage.
Ask another questionIt can remove a great deal of repetitive interface and configuration work, but it does not pretend desktop engineering has no code. You can build visually, inspect the generated source, and extend normal React, Vue, Svelte, TypeScript, or Rust files when the project needs it.
Yes. The current product exports a complete Tauri 2 source tree that runs without Paneweaver. The free Local plan is intended to keep source export available.
The browser edition supports visual editing, state and actions, project import analysis, preview, validation, source inspection, backups, and ZIP export. The desktop edition additionally writes projects to disk, detects local toolchains, starts the Tauri development workflow, streams logs, and tests real native behavior.
Not in the current local edition. Projects stay in the browser profile or desktop WebView unless you export a Paneweaver backup or source archive. Account-based cross-device sync is planned for the private beta.
No. Generated projects include a GitHub Actions release workflow, but Paneweaver does not yet connect repositories, push commits, manage branches, or create pull requests. Those capabilities are planned for the cloud plans.
Yes. Paneweaver can analyze a selected project without installing dependencies or running scripts, preserve compatible source, and add a Tauri 2 wrapper. Imported source remains code-managed unless Paneweaver has an explicit visual mapping for it.
The current full visual generators support React, Vue, and Svelte with TypeScript. Existing frontends that produce compatible static assets can also be wrapped in code-managed mode.
Paneweaver Studio
Request access to the private beta or begin evaluating the local-first workflow.