Small idea. Real foundations.
Create a separate development project, keep every source version and see exactly what has been checked.
YOUR CREATIVE WORKSPACE
Loading isolated development environment…
Counts come from your private staging records.
Published sites, service alerts, analytics and live hosting usage are unavailable here.
Create a separate development project, keep every source version and see exactly what has been checked.
First scope: static HTML, CSS and JavaScript. Bookings, accounts, payments and other server features require a later phase.
Provider execution is locked. Browser quality checks and publishing are not yet connected.
Only recorded events appear here. A queued agent has not performed its work.
Preview is a restricted, offline frame. Forms, external resources and top navigation are blocked.
The Director activates relevant specialists. Independent platform controls enforce budgets, permissions and a maximum of two parallel advisers. Specialist advice does not provision services.
Source audits run as durable, non-billable jobs. Every result belongs to an exact saved revision. They are source checks, not executed browser tests or a security certification.
Untrusted browser jobs require a dedicated non-root runner with the Chromium OS sandbox. No such runner is connected yet; checks cannot silently use an unsafe browser.
Guided help is working and uses rules without AI calls. The optional live AI Director uses an authorised trial allowance after a build or scope decision. No automatic actions are performed.
Connection, ownership verification and DNS integration pending. No availability or price is invented.
Transactional sending and full mailboxes are separate services. Provider setup and tenant isolation are pending.
Private previews are available for saved static source. Public hosting and customer deployments are pending.
No domain registration, renewal, mailbox purchase or deployment is performed.
Registrar integration is not connected. Real availability, registration and renewal prices must be retrieved before purchase approval.
No mailboxes have been created. Existing production email configuration is preserved. Resend transactional sending must not be described as an inbox.
Public deployment is not enabled in this environment. No project is published by saving, previewing or accepting source files.
Each saved version remains private to your account.
Restoring creates a new version. Earlier source remains available.
Moving a project to trash hides its source and private files. Revisions are retained. Active execution must finish first. No permanent project purge is provided.
The existing inference ledger reports development usage in US dollars before tax. Payments, funded balances, invoices and separate service charges are unavailable.
Open a project first. The estimate uses a standard static website scenario with the saved brief attached. Saving or accepting it starts no work, payment or spending.
Staff roles do not grant private content access. Choose your project to review its support grants and access history.
Real session expiry and local provider logout tests
Private storage, recovery and session checks
Development projects are separate from production projects. Sign in using your existing Pevrino email and password. Password changes are not performed here. A separate verified test identity can be requested through the dedicated signup form.
Create a separate verified test account
Use two dedicated real Pevrino accounts. This creates only labelled staging fixtures, with no AI calls, publishing or authentication changes. Share the signed fixture package between the two accounts; it contains test identifiers and hashes, never a login token. Each direction must pass separately.
Creates a new separate workbench for editing and restoration. Preserved projects are not edited. Requests stay queued with zero AI calls. Private storage and recoverable deletion are verified separately.