Frequently asked questions

What is PhiWebs?

You describe an app in plain language and PhiWebs builds it — the pages, the records behind them, and the sign-in your visitors use — then publishes it at your own address. The source stays yours to download and run anywhere.

What exactly is an app?

Three things that arrive together:

• Pages — several of them, not a single screen.
• Data — the records your pages read and write (bookings, members, articles, whatever the app is about).
• Visitor sign-in — the door the people who use the app come through.

You do not assemble those separately. Ask for a gym schedule with a membership form and all three are wired together. See What an app is.

Is it a website or an app?

Both, depending on what you asked for. A public marketing site is an app whose pages are open to everyone; a customer portal is an app whose pages sit behind a sign-in. Same machinery.

Where does my app live?

At its own address, shown to you the moment you publish:

your-name.phiwebs.app

Apps published before that address existed may still answer on the older -apps.phiwebs.com form. Both keep working.

Can I use my own domain?

Yes, on Team plans and above. Point your domain at the app and it answers there instead. See Publishing.

Who can open my app?

Whoever you decide. Pages can be public, or they can sit behind a sign-in that your visitors use — email and password, Google, GitHub or Microsoft, or your own OIDC provider.

A visitor account is not a PhiWebs account. Someone signing in to your app is not a member of your World and cannot open the builder. See Visitor sign-in.

Can I take the app with me?

Yes, on every plan, and this is not a paid extra:

• pwpack — the app’s full source in one package.
• pwapp — a ready-to-run bundle you can drop on any static host.

Closing your account does not take the work with it. See Publishing for both routes.

What is Φ, and what happens when it runs out?

Φ is the credit that meters building and AI. Your plan loads an amount each month; building a whole app spends more of it than reworking a page, and a short chat spends very little.

When it runs out, new building pauses — your published apps stay up and their addresses keep answering. Top up, and building resumes. See Billing.

How does pricing work?

Plans are shaped around how many apps you keep live, how much you build, how many visitors and records you have, and what your team needs. You choose one at checkout when you sign up and can change it later from your Billing page; Enterprise is arranged with us from the contact page. Prices are on the pricing page.

How does team collaboration work?

Team plans and above let more than one person work in the same World. Each member holds a role — owner, admin, editor or viewer — that decides what they may do, and the World’s audit log records who did what.

Every change is proposed as a Receipt before it lands, so what changed and why stays readable afterwards. See Collaboration.

Can I publish what I built for other teams to install?

Not today. The marketplace carries blocks and starters published by us; it is not open to listings from other teams. What you build stays yours to download and hand over as a pwpack — see Starters.

Can I change the branding?

Yes. Colours, fonts and logos are theme tokens applied across the apps in a World, on every plan.

Can another system read my app’s data?

Yes — the platform API reads and writes the same records your pages use, so an app can sit alongside whatever you already run. See the API reference and rate limits.

Is PhiWebs secure?

Worlds are isolated from one another: apps, records and members never cross between them, and each World has its own audit trail. Every proposed change is a readable Receipt before it ships, staff actions are audit-logged, and data-subject access and deletion requests are handled through a documented flow. We share controls, architecture overviews and pen-test summaries on request.

Still have questions?

Write to us at phiwebs.com/en/contact.