Acquisitions create a peculiar kind of app-builder anxiety. The old domain still loads and reviews still rank, but the login route belongs to another product. That is where Vly sits in September 2026.
This Vly AI review is therefore not a tour of its 2025 feature list. I followed the live migration route, submitted a fictional app brief to Freebuff Web, reached its style picker, and stopped when login became necessary. I did not access an existing Vly account, so project continuity and deployment are not presented as hands-on results.
Quick Verdict: Vly Now Continues Through Freebuff
Vly is no longer the product a new user should evaluate on its own. The live Vly acquisition notice directs new accounts and existing project access to Freebuff Web. It instructs users to create a Freebuff account with GitHub and says former Vly subscriptions will be canceled.
Existing users should try the migration before rebuilding. Continue only if the project, data, domain, and code remain usable under the new account. A founder starting from zero should evaluate Freebuff Web as today's product, not rely on an old Vly app builder review.
What Changed After the Freebuff Acquisition
Freebuff describes Vly as the earlier web product, now folded into its coding-product family. A March announcement updated in July says the engine, templates, dashboard, projects, deployment URLs, GitHub export, and custom domains carry over.
Those are company statements, not an independent migration audit. The live notice is more specific: create the Freebuff account with GitHub, then use Settings to transfer projects when the GitHub and Vly emails differ. I would follow that current instruction first.
New Accounts, Project Access, and Canceled Subscriptions
Three changes matter immediately:
| Area | Current public instruction | What the user should verify |
| New account | Continue through Freebuff Web and create an account with GitHub | Correct GitHub identity, organization access, and recovery email |
| Existing projects | Projects should carry over; different emails may require a Settings transfer | Project list, code, data, domains, secrets, and live URLs |
| Vly subscription | The live notice says existing subscriptions will be canceled and users will not be charged again | Final invoice, cancellation state, and any separate Freebuff plan |
The cancellation applies to Vly subscriptions. It is not a promise that every Freebuff service will remain unlimited or subscription-free. Freebuff's terms allow paid plans that add session capacity, with limits and model availability shown inside the account.
Separate Historical Vly Features From the Current Product
Search results still surface detailed Vly feature descriptions. They remain useful for understanding what an older project may contain, but they are not evidence of what a new Freebuff account includes today.
What the Old React, Vite, and Convex Documentation Can Still Prove
The still-accessible Vly documentation describes React, Vite, Convex, Tailwind CSS, checkpoints, collaboration, automatic deployment, and custom domains. It tells an owner what to look for: a React codebase, Convex-backed records, assets, checkpoint history, and deployment configuration.
It cannot prove that those elements transferred, or establish current Freebuff pricing, privacy, agent choice, export behavior, or support. Check continuity inside the migrated project rather than infer it from similar product language.
Move One Existing Project to Freebuff Web
Do not begin with a redesign. Inventory the Vly project name, public URL, domain, last working screen, authentication providers, important records, environment variables, connected services, and each external-account owner. Export or sync the code to GitHub if available.
Create Freebuff with the GitHub identity you intend to keep. If its email matches Vly, check for the project. If not, use the transfer option named in the live notice. I could not verify that control without an existing account, so its fields and timing remain unconfirmed.
GitHub Identity, Account Transfer, and Project Access
Treat GitHub identity as part of the handoff. Confirm who owns the repository, who can revoke Freebuff access, and whether the client retains access when a contractor leaves.
Before changing anything, check the project tree, one known record, one protected route, one asset, and the production URL. Test a custom domain from a fresh browser. Keep old URLs and screenshots until the new route works. A dashboard card alone does not prove the app survived.
Test the Current Build-and-Deploy Path
On September 29, 2026, I used a fictional brief: "Build a service-request tracker with GitHub sign-in, a request form, saved status, an admin view, and a clear error state when saving fails."
The public Freebuff Web builder accepted the brief and opened a style picker with options including Minimalism, Modern, Studio, and Terminal. Selecting Minimalism then led to a login screen offering GitHub, Google, or Apple. I stopped there; no project was generated or deployed.
This establishes that the public build funnel is active and style selection precedes authentication. It does not verify full-stack generation, hosting, deployment, domains, or production readiness.
After login, repeat the brief, then add one awkward revision: staff may update status but cannot view other clients' requests. Interrupt a save and check for duplicates after reconnecting. Record the agent, failures, data behavior, live URL, and any paid-session prompt. Until then, "free" and "deployed" describe the offer, not operating cost or reliability.
Who Should Continue—and Who Should Reconsider
Continue when the project appears under the intended GitHub identity, critical data is present, the URL works, and the business controls the repository. Passing those checks may make continuity more sensible than rebuilding.
Pause when ownership is unclear, a transfer is missing, or a domain points to a project nobody can administer. Reconsider if procurement requires accessibility documentation, stable model commitments, formal support, or strict repository controls.
The current Freebuff terms cover Web, Cloud, Chat, Desktop, and its coding tools. They state that users retain submitted content and own generated output to the extent allowed by law. Review current privacy disclosures before connecting a client repository; an acquisition does not erase that responsibility.
When a Fresh HappySeeds Build May Make More Sense
HappySeeds becomes relevant only when preserving the Vly implementation is no longer the main goal. If the old project was a rough experiment, rebuilding one clear customer workflow may be more useful than spending days recovering screens that never became a coherent product.
Use the Vly project as evidence, not as a specification. Identify the records worth keeping, the users who need access, the action they must complete, and what should happen when that action fails. HappySeeds can then turn those decisions into a new Web App and support small, reviewable revisions through chat and Preview. Any database, account access, payment, or publishing setup still needs to be configured and tested for the new project.
This is a rebuild decision, not a Vly Freebuff migration path. Stay with Freebuff if the transferred project keeps its code, data, domain, and working behavior. Consider rebuilding when migration succeeds technically but leaves the team supporting a product flow that was never properly defined.
Keep the Project Only If the Handoff Holds
Vly's acquisition does not make every project obsolete; it changes the evidence required. The migration route is live, the public builder is active, and ownership terms exist. What remains personal to each owner is whether code, data, domain, and operating controls survived. Verify that handoff first. Brand continuity is reassuring. Project continuity is the reason to stay.
Explore More Topics:
FAQ
Are Vly Trustpilot reviews attributable to the pre-acquisition product?
Not automatically. Classify each review by date, named features, pricing references, and whether it mentions Vly or Freebuff. Do not merge pre-acquisition and post-migration feedback into one score.
Does Freebuff publish terms for ownership of AI-generated code?
Yes. Current terms say users retain submitted content and own generated code, text, and assets to the extent permitted by law. They also warn that output may not be unique. Still review open-source, client-contract, and third-party-license obligations.
Can Freebuff users choose which coding agent handles a migrated project?
Freebuff displays Vly Agent 2.0, Claude Code, OpenAI Codex, and Gemini CLI, but public material does not establish which agents every migrated project can select. Confirm the in-account selector before promising one.
Does Freebuff provide accessibility documentation for generated apps?
I did not locate a public accessibility conformance report or VPAT for Freebuff Web. That does not prove inaccessibility. Request current documentation and test generated apps with keyboard, screen-reader, contrast, and zoom checks.
Where can users report a security issue affecting a migrated Vly project?
Freebuff directs vulnerability reports to [email protected], not public issue trackers or social media. Include reproducible steps, affected project identifiers, impact, and safe contact details, but never live credentials or unnecessary customer data.
