Is generated-app login separate from Uvilno's creator account?

A direct answer, the limits that matter, and a practical way to check the workflow.

Direct answer

Uvilno's app authentication uses project-scoped visitor identities and sessions, separate from the creator's platform login. Configured Google, GitHub, Discord and email flows must not replace builder cookies. Verify both identities around sign-in, sign-out and reload; a separate login page alone does not establish session isolation.

45-word answer · Reviewed 2026-10-27

The creator and the visitor have different jobs and privileges. A website visitor should never become the builder account simply by completing an OAuth flow in the preview. Tokens and callback state must remain scoped to the intended project and application origin.

Test at least two projects and two disposable visitor identities. Sign into the generated app, reload it, sign out and confirm the platform still shows the original creator. Exports need their final supported HTTPS origin registered; copying a callback URL from the builder is not a migration strategy.

What to verify.

Compare products
Documented behavior and checks the reader can perform
AreaDocumented behaviorYour verification
Visitor identityManaged sign-in is scoped to the generated project.Check the app user before and after authentication.
Builder identityPlatform cookies remain independent.Keep the creator profile open while testing sign-in.
Exported originHosted sign-in needs approved origin configuration.Test the final host's redirect and session flow.

Drag the slider, use the arrows, or scroll within the table.

Try the workflow yourself.

Use this checklist in your own disposable project. These marks record your review; they do not run tests or certify an application.

0 of 3 review steps marked by you.

Read the editable test brief

Plan a project-scoped account flow with Login, Register and Profile for a private application. Use only the managed app authentication interface, never the creator's platform session. Include clear failed and pending confirmation states, a real sign-out action and a test that the builder user stays unchanged throughout app login and reload.

Preparing a brief does not start generation. Review and send it explicitly; builds use the normal allowance, and source access requires entitlement.

Sources and scope.

Published by the Uvilno editorial team on . This is product documentation and editorial guidance, not an independent ranking or a promise that every application will pass. Vendor plans can change; official sources establish their own terms.

Does opening this test use my allowance?

Preparing the test brief does not invoke a model or create a billable build. Review the draft and explicitly send it to generate; normal usage and source entitlement rules apply.

Check the architecture. Compare the tradeoffs.

Follow the data model, account boundary and source handoff before choosing a builder.

Compare builders

Plan a full-stack app

Review the evidence

Read the public Markdown reference