AVAILABLE
Community
Use the open-source tools fully, without docs walls or paid-only Issues.
FreeAvailable now
- All open packages and docs
- Public GitHub Issues
- Local CLI and starter template skeletons
Delivery and support
Support open source first, then choose a service
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
From one trial to a reproducible delivery path
PLANNED
Pro
A future personal productivity path for templates and cloud builds.
PlannedNot open yet
- Complete official templates
- Cloud builds and preview output
- Build history and bundle analysis
PLANNED
Team
A future path for small-team collaboration and private components.
PlannedNot open yet
- Team roles and collaboration
- Private component registry
- Shareable build records
PLANNED
Enterprise
A future path for security review, internal deployment, and long-term support.
PlannedNot open yet
- Dedicated deployment and security
- Version pinning and audit
- Dedicated delivery support
01A / OPEN-SOURCE SPONSORSHIP
Sponsor weapp.dev open source
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.
Supporter
¥20one-time / permanentPermanent public thank-you.
Request sponsorship detailsBronze sponsor
¥200one-time / permanentAfter identity confirmation and authorization, show a GitHub avatar, username, and profile link.
Request sponsorship detailsSilver sponsor
¥1,000one-time / permanentFeatured individual recognition, including Bronze benefits.
Request sponsorship detailsGold business partner
¥2,000+by partnership termSingle-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
Confirmed sponsorship is split net of payment fees: 60% core maintenance, 25% contributors fund, 15% nearby open source. If the quarterly fund is under ¥500, it rolls forward. Ledgers are published each quarter.
Core maintenance
Maintainer time, testing, CI, domains, and the docs sites.
Contributors fund
Quarterly payouts for eligible work; up to 40% may be bounties.
Nearby open source
Upstream projects in the mini-app ecosystem.
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.
Public recognition (confirmed and authorized GitHub or business details only)
gold
02 / ROADMAP
Capabilities in development
Cloud builds, official templates, and private component registries will open after a stable delivery path exists. Varo remains planned component inventory and is not charged against a GA date.
The first official templates
This is a direction, not a live catalog or purchasable inventory. Future publishing will be invite-only and focused on reviewable, rebrandable scenarios.
Store redemption
Local services
Store, coupons, redemption, orders
Booking
Healthcare / beauty / education
Services, calendar, checkout, reminders
Membership card
Brand
Activation, points, tiers
Content subscription
Publishing
Feed, detail, paywall
Light commerce
Commerce
Catalog, cart, orders
B2B showcase
Company site
Cases, lead forms
03 / CLOUD BUILDS
Cloud builds are still in development
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.
- 01Pull from GitHub / Gitee
- 02Build for a target
- 03Upload trial version
- 04Return QR, logs, and bundle report
04 / SERVICES
Implementation tied to the toolchain
Single page / repository migration
Adopt weapp-vite + Tailwind and leave CI green.
Full project migration
Routes, sub-packages, multi-target output, and bundle baseline.
Enterprise training
Up to 20 people, including a lab repository.
Template customization
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
Current support boundaries
| 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
The open-source boundary is explicit
Always open
Compilers, plugins, local CLI, starter template skeletons
Potentially paid later
Cloud queues, complete official templates, private registries, and enterprise support only after real delivery exists.
Never
License checks in MIT packages, docs walls, paid-only Issues
07 / FAQ
Frequently asked questions
What do sponsors receive?
Sponsorship supports open-source maintenance and does not include technical support, template source, cloud-build minutes, or other commercial benefits.
How is sponsorship income used?
Net receipts split 60% core maintenance, 25% contributors fund, and 15% nearby open source. The contributors fund pays quarterly and rolls forward under ¥500. Future Pro, Team, and implementation revenue stay out of this fund.
Is the contributor program employment or contracting?
No. It is an open-source thank-you, not a job or paid engagement, and it does not buy copyright. Full rules are on the contributor program page.
Can I buy Pro, Team, or Enterprise today?
No. These capabilities are still in development. The page describes direction, not an open checkout or payment commitment.
Give open source a budget to keep going
Until a payment flow exists, use GitHub to request sponsorship details or discuss a human-delivered migration scope.