Zite test data

The Fitting Room brief was pasted word for word (1,689 characters) into Zite's home page on the free plan on 27 October 2026. The clock stopped when the app was live on its address and the checks that need no keys passed.

Zite answered in about 30 seconds. It had set up the app with sign-in and nothing inside, and said it needed Stripe (test mode) and an email account connected before it could build the rest. I did not connect them. My second message told it to build everything else in the brief except those two parts, and it took about 7 minutes.

I clicked Publish about 11 minutes after the brief and the zite.so address answered about 20 seconds later. The app live then is the one that passed 22 of the 24 checks that need no keys of mine, from two messages and no fix prompt. The first build used 0.5 credits and the second 5.7.

• I ran the 24 checks after the app was live, not at the 11-minute mark; the app did not change in between.

The brief's written checks were run on the live app with a separate browser session for each role: a member, a second member, a coach, and two admins. The six that need a Stripe or an email account of mine (C24 to C29) were left out, which leaves 24, and the thresholds are applied in proportion: 5 needs 93 percent, 4 needs 80 percent.

22 of 24 passed. C01 (sign up with an email and a password) and C03 (a password reset email and a new password) failed, because Zite does not use passwords. Its chat said: "Sign-in works by emailed link, not password." Sign-up, log-in, log-out and the role screens all worked with that link, which arrived in about ten seconds.

Everything else passed: the timetable with the three classes and their coaches, places left, booking, My bookings, cancelling and the place freed, the capacity rule (checked in the page and by calling the booking request directly), a member with no credits told to buy a pass, the coach seeing only their own classes with the booked members and a saved attendance mark, the admin adding, editing and deleting a class, all bookings, a CSV file with the right columns, the count per class, and the Ask the studio form with the admin seeing the message. Nothing was invented: instead of a pass purchase the app says "Online pass purchase isn't available yet", and the admin adds credits by hand.

• The six payment and email checks were not run. The brief asks for passwords; Zite offers a different sign-in, so I counted C01 and C03 as failed rather than waive them.

Sign-up, log-in and log-out for two members, a coach and two admins, then two attacks with the app's own requests, replayed with the wrong session: asking for another member's bookings, and calling admin-only actions as a member. I also called the admin requests as an admin waiting for approval and as a visitor with no sign-in.

Both attacks were blocked. The member's bookings request takes no member id: adding another member's email or id changed nothing and it returned only my own rows. Every admin request (all bookings, delete class, edit class, add class, change a person's role and credits, mark attendance) answered "You do not have access to this." for a member. A booking request for another member's booking returned "Booking not found." A visitor with no sign-in was refused with an error that says the endpoint requires authentication.

Staff need approval, with one gap. The welcome page lets you pick Member, Coach or Admin and says "Staff accounts are approved by a studio admin." The first person to sign up as admin is approved at once; Zite's chat said so, and told me to sign in first as admin. My second admin waited, and calling the admin requests while waiting was refused. A stranger who reached a new app before its owner would take the admin role.

There are no passwords. You get a link by email and the sign-in finishes with a click on a confirm button. There is no password reset to test.

• Zite's own security scan was not found on the free plan and was not run. The requests were replayed by script with each account's session cookie, on my own app.

The six data checks: the form and bookings write real records, they survive a reload, republishing and a design change, the admin can view, filter, edit and delete records, and the data exports as a file.

Proved (six): the Ask the studio form and the bookings wrote records; they were still there after reloads and after every republish, including the colour change; the admin viewed, edited and deleted classes in the app (it asked "Delete Test Stretch?" before deleting and gave the member's credit back); the data panel has a grid with sort, filter, hide fields and a record editor, and an edit I made there showed in the app; and the bookings downloaded as a CSV with the right columns, from the admin screen and as a table export in the panel.

The data panel shows four tables: Profiles, Classes, Bookings and Studio Inquiries. Deleting a class cancels its upcoming bookings; a booking row of the deleted class stays in the member's list as "Removed class".

• Backup, restore and the history view were not tried. A delete of a row in the data panel was not run; deleting a class in the app was.

The twelve scripted changes, one message each, on the live app, which I republished after each. After each change I ran a short check that booking, My bookings, cancelling and refunding a credit, the coach screen and the admin screens still worked. I checked the balance before every message and never clicked Upgrade.

Seven of the twelve ran, and all seven worked: a phone field on member sign-up, shown on the admin's People tab (E01); instructor renamed coach everywhere (E02); dark green and cream (E03) and an About page (E04), which Zite received as one message and did both; Power Reformer's capacity set to 4 with a stricter rule that stops an admin lowering capacity below the bookings taken (E05); a coach filter on the timetable (E06); and the planted credit bug, which Zite planted when I asked and undid when I reported it (E07).

Two small snags. After E05 Zite told me its home page card still said "up to 6", and its next message turned the cards into live data. E06 stopped part way with a "fetch failed" note and 4 pending changes; one click on Resume finished it. The planted bug cost one member credit in my own checks, which the fix then stopped. Zite warned me: "A member may have missed a credit: there are 13 cancelled bookings in your data."

The tenth message of the day was the email change (E08). Zite did not build it: it offered its own Email integration to connect and its chat then said: "No messages remaining today. Upgrade for more messages, or build with your own AI." E09 to E12 were not run. The seven changes and the E08 attempt used 19 of the 25.5 credits, and the dearest were the planted bug (3.5) and the first change (3.1).

• The five unrun changes (the email, the phone layout, the admin-only export, the waiting list and the dark mode) could have moved this grade either way. The 24 checks were not re-run in full after each change, only a short check. One credit balance read failed after E04 because my second tab was signed out; the next read gave the missing figure.

Publish to the zite.so address, try to connect a custom domain, three Lighthouse phone runs on the home page, and a width check at 360, 390, 768 and 1440 pixels on six pages with the member and admin accounts.

Publishing took one click and about 20 seconds, with HTTPS on the zite.so address. The custom domain page says "Upgrade your plan to connect custom domains to your apps and forms, and unlock much more." so the test domain was not connected. The pricing page lists one custom domain on Pro and unlimited on Business. The Zite badge, "Made with Zite", stays on the app on Free. The page has no robots tag and no web manifest.

The phone speed score of the home page was 70, 78 and 78, a median of 78, with the main content at about 4 seconds on a simulated phone. The log-in screens, the timetable and the admin screens could not be measured by the tool.

No page scrolled sideways at any of the four widths. On a phone I counted 2 faults: the menu runs out of room so the last tab, Ask the studio, is cut off, and the "Made with Zite" badge sits over the content.

Some app requests were very slow just after a republish. The same request took from under a second to 48 seconds on one afternoon. The pages themselves loaded quickly.

• No custom or test domain, no 100-class seed, no logged-in page speed, no real phone and no add to home screen. Pro is where the domain starts.

The Code tab, the Source control panel, the app menu, the workspace and organisation settings, the data panel's table menu, and Zite's public terms page.

I found no way to download the code on the free plan. The Code tab shows every file of the app, a React project with an api folder, components and pages, and I could read them, but there is no download button. The Source control panel says "Coming soon" next to GitHub, GitLab and Bitbucket. The app menu offers copy link, duplicate and move, not export.

Data is different. Any table exports as CSV from the table menu, and the admin's bookings file downloaded. Zite's home page says "Own your data and export anytime." The REST API is a switch in Developer settings (Enable API); I did not turn it on.

The terms page on zite.com is Fillout's terms of service for Restly, Inc., with an effective date of July 2022, and I found nothing in it about who owns an app built with Zite. I asked support.

• Paid plans were not tried: a download or a repository link may exist there. The code was not run anywhere else, and the terms were not read in full.

The pricing page (billed-yearly and monthly views), the billing page with the credit meter and the Limits tab, and the custom domain page were read on 27 October 2026, with a screenshot at each step. Zite charges in credits, with a daily message limit on Free.

I paid nothing. The free plan gave 50 credits for the month, and a welcome checklist added 50 for signing up with a work email and 50 for publishing, which expire on 31 October. The test used 25.5 of the 150: the first build 6.2 and everything else 19.3. At Pro's price of $25 for 100 credits, 25.5 credits is about $6.40, so the build and seven changes are cheap if you can send the messages.

The limits are the cost. Free allows 10 messages a day (I used all 10), one workspace, 5,000 records and 1,000 workflow runs a month, and my own checks used 553 runs. Pro is $25 a month, or $20 a month billed yearly ($240 a year), with 100 credits, no message limit, one custom domain and no Zite badge. Business is $89 a month, or $75 billed yearly. No card was needed and nothing can bill beyond the plan. I have not read what 1,000 bookings a month would cost.

• The yearly view was read, not bought. Team and Enterprise were not priced. The monthly price per credit on Pro is my arithmetic from the price and the 100 credits.