Community
Use the open-source tools fully, without docs walls or paid-only Issues.
- All open packages and docs
- Public GitHub Issues
- Local CLI and starter template skeletons
Delivery and support
Core compilers and plugins stay MIT open source. This page lists human-delivered services and sponsorship; other commercial capabilities are still in development.
01 / PRODUCT SHELF
Use the open-source tools fully, without docs walls or paid-only Issues.
A future personal productivity path for templates and cloud builds.
A future path for small-team collaboration and private components.
A future path for security review, internal deployment, and long-term support.
01A / OPEN-SOURCE SPONSORSHIP
Chinese open source needs sustained time, infrastructure, and maintenance. Sponsorship is not a service purchase; it helps this toolchain keep shipping and supporting its community.
Permanent public thank-you.
Request sponsorship detailsAfter identity confirmation and authorization, show a GitHub avatar, username, and profile link.
Request sponsorship detailsFeatured individual recognition, including Bronze benefits.
Request sponsorship detailsSingle-site monthly ¥2,000 / 30 days; dual-site monthly ¥3,000 / 30 days; dual-site quarterly ¥8,000 / 90 days; custom terms by discussion.
Request sponsorship detailsWhere it goes
20% of sponsorship income goes to mini-app ecosystem open-source projects. The rest funds weapp.dev maintenance, documentation, testing, build infrastructure, and community operations. We will publish the destinations monthly or quarterly.
Sponsorship is not a service purchase and does not include technical support, template source, cloud-build minutes, or subscription access. Public display requires GitHub identity confirmation, maintainer review, and explicit authorization; approved records may appear on weapp.dev, tw.weapp.dev, and vite.weapp.dev.
gold
02 / ROADMAP
Cloud builds, official templates, and private component registries will open after a stable delivery path exists. Varo is published independently; its open components and source are not part of GA pricing for these future commercial capabilities.
This is a direction, not a live catalog or purchasable inventory. Future publishing will be invite-only and focused on reviewable, rebrandable scenarios.
Local services
Store, coupons, redemption, orders
Healthcare / beauty / education
Services, calendar, checkout, reminders
Brand
Activation, points, tiers
Publishing
Feed, detail, paywall
Commerce
Catalog, cart, orders
Company site
Cases, lead forms
03 / CLOUD BUILDS
The future path is to pull from GitHub / Gitee, build for a target platform, upload a trial version, and return a QR code and logs. No availability or quota is promised today.
04 / SERVICES
Adopt weapp-vite + Tailwind and leave CI green.
Routes, sub-packages, multi-target output, and bundle baseline.
Up to 20 people, including a lab repository.
Per-page customization, or 15% revenue share after listing.
Services stay tied to the toolchain and do not become unrelated product outsourcing. New work pauses if services exceed 50% of total revenue for two consecutive months.
05 / SUPPORT
| Tier | Channel | Response |
|---|---|---|
| Open source | GitHub Issues | Public discussion, no time promise |
| Human services | GitHub contact | Confirmed per project scope |
| Sponsors | No dedicated support | Sponsorship does not buy service benefits |
06 / OPEN-SOURCE BOUNDARY
Compilers, plugins, local CLI, starter template skeletons
Cloud queues, complete official templates, private registries, and enterprise support only after real delivery exists.
License checks in MIT packages, docs walls, paid-only Issues
07 / FAQ
Sponsorship supports open-source maintenance and does not include technical support, template source, cloud-build minutes, or other commercial benefits.
A fixed 20% goes to mini-app ecosystem open-source projects. The rest funds weapp.dev maintenance, documentation, testing, build infrastructure, and community operations.
No. These capabilities are still in development. The page describes direction, not an open checkout or payment commitment.
Until a payment flow exists, use GitHub to request sponsorship details or discuss a human-delivered migration scope.