Custom Wix Studio development, without moving off the platform

Velo is Wix's development platform: JavaScript that runs on the site, both in the browser and server side. It gives a developer access to the page, the CMS collections, external APIs, scheduled jobs, and the site's own events. In practice it's the difference between a site that displays content and a site that does something with it.

Anything driven by data or logic rather than layout: filtered search across large record sets, marketplaces with multiple sellers, member areas with permissions, quoting and configuration tools, documents generated per submission, and automations that move information between systems. Standard Wix builds pages. Wix Studio with Velo builds behaviour.

Yes, and we've shipped one. Yacht Junky is a two-sided boat and yacht marketplace built entirely native: sellers list, buyers filter by specification, enquiries route to private sellers without publishing contact details, sellers get notified, and prices convert between currencies. No external stack, and the team runs it without a developer on retainer.

Web applications with logins, permissions, saved records, and custom logic, yes. Native mobile apps for the App Store or Google Play, no, that's a different technology entirely. If what you're describing is really a mobile app, we'll tell you at the scoping call rather than three weeks in.

When the product needs transactional complexity the platform doesn't cover, escrow, multi-party payouts, deep seller dashboards, when record volumes and query complexity would strain it, or when the site itself is the product rather than the front of a business. We build custom too, including this site, so the recommendation isn't a hammer looking for nails.

It's quoted per project, and it's the only service here without a published floor. Scope varies too much between an integration and a platform for a starting number to mean anything honest. You get a fixed price in the technical proposal a few days after a free scoping call, before any work begins.

Most projects run two to five weeks of build after scoping, with the data architecture in week one. Yacht Junky's full marketplace took four weeks. Integrations and automations are usually faster than platform builds, because the data model already exists.

Yes, and that's a common engagement. We audit what's there, work out whether the current structure supports what you want, and build onto it. If the existing CMS structure would fight the new feature, we'll say so and price the restructuring separately rather than building on a foundation that will cause problems later.

Anything with an API, which today is nearly everything: CRMs, booking systems, payment providers, accounting tools, email platforms, and internal software. Just Stay's property list syncs from Bookeddirectly through Zapier, so what's live on the site is always what's actually bookable. Where a direct API connection is cleaner than a middleman, we build that instead.

That's often the highest-value thing we do on an existing site. Enquiries routed and assigned automatically, records created in your CRM without retyping, follow-ups triggered by behaviour, internal notifications when something needs a human. The rule of thumb: if a person does it the same way every time, it can probably be automated.

Yes, and protecting that is part of the design. Content, records, and settings stay editable in the normal Wix interface. What's code is documented in the handover, so everyone knows which parts are safe to change and which need a developer. Losing editability is the usual cost of custom work, and it's avoidable.

Every project includes a support window after go-live, which is when real traffic finds the edge cases testing missed. Beyond that, fixes are available as needed rather than through a mandatory retainer. Well-built Velo doesn't need constant attention, and we'd rather you call us because you want something new.

Yes. Logins, roles, permissions, and content restricted to specific groups, whether that's a client portal, course material, partner resources, or pricing you'd rather not publish. Member data lives in the CMS like any other collection, so it's queryable and connectable to the rest of the site.

Badly written code does, on any platform. Written properly, server-side logic runs before the page reaches the visitor and the pages stay indexable, which matters because dynamic CMS pages are often the ones you most want ranking. Bel'Istria runs 70+ dynamic pages generated from collections, all indexed and ranking.

Usually, and it's worth asking before assuming a plugin's function has no equivalent. Most WordPress plugin functionality is either native in Wix Studio or straightforward in Velo. The migration service covers moving the site itself; this covers rebuilding what the plugins were doing.

You do. It lives in your own Wix account with the rest of the site, documented in the handover. There's no licence to renew, nothing hosted by us, and nothing that stops working if we part ways.