00 · Product

What every WisyLink site gets

A plain, section-by-section reference for what the product includes, what it can and can't do, how it stays reliable, and how it's supported.

No vendor names. No invented metrics.

01 · Foundations

A real site, not a template

Every site is a real, independent product — not a shared template. Here's what that means for you.

1.1

Kept apart from every other site

Every site you build runs on its own, separate from every other WisyLink site.

1.2

A real backend from the first build

Each site gets its own database and file storage, and — when it needs them — real accounts, payments, and live channels, wired in from day one instead of bolted on later.

1.3

Published automatically

When a build finishes, your site is published automatically — no manual publishing step.

02 · Scope

What it does — and what it doesn't

What gets produced is a real, production-grade product. Here's exactly what that includes, and where the intentional limits are.

What's included

2.1

A real, hosted web app

Pages on their own domain, with content that search engines can read — not a static mockup.

2.2

A working backend, not just a front end

Data storage, file uploads, and — when the site needs them — accounts, payments, and live updates, already wired in.

2.3

Your own address

A hosted subdomain by default, or your own custom domain connected through the platform.

2.4

Keeps working while you keep changing it

Every change either ships cleanly or leaves the previous version live.

The intentional limits

2.5

It never spends on your behalf silently

Any action that consumes billable usage beyond your plan's included allowance runs only after you explicitly trigger it — never automatically.

2.6

It doesn't hold your third-party accounts

Payment processors, email, and any other service you connect use your own accounts and credentials.

2.7

Usage has limits that come with your plan

Storage, database, and bandwidth have limits defined by your plan.

2.8

It builds real web backends, not app-store binaries

What you build is a web application, reachable from any browser and any device — not a compiled app submitted to an app store.

03 · Reliability

Built to stay up, not just to launch

No platform is immune to failure. Each site runs on its own, so a problem stays limited to that site.

3.1

Contained failure

Because every site runs on its own, a fault on one site is kept from spreading to another.

3.2

A failed build never reaches visitors

If a new version doesn't finish successfully, the site simply keeps running on the last one that did.

04 · Support

How support requests are handled

Send a question or a support request through the contact channel — here's what happens once it arrives.

4.1

Every message reaches our team

A question or issue you send through the contact form reaches our team.

4.2

If it needs a person, you'll hear from us

When a report needs a reply, we get back to you directly.

4.3

It starts with a message

Send a question or a support request through the contact form.

See it for yourself

The fastest proof is a real one — describe what you want and watch it get built.

Let's build something together

From a sentence to a live app.