Local Desktop
Runs on the connected device. Project data stays on that device unless sync is enabled.
Control Trace
See which identity, Space and execution authority a run will use before data moves or account quota is admitted.
First steps
Execution location
Choose where work executes. Location changes data movement, available capacity and billing authority.
Runs on the connected device. Project data stays on that device unless sync is enabled.
A provider-managed environment must be provisioned and approved before it can receive execution data.
Connect an administrator-approved Company endpoint from Desktop before routing work there.
Your Space runs on the shared Mockarty — open it with one click. An isolated instance of your own is a separate offer; when it is available here, the form below appears.
Sign in to the new instance with this login and password, then change the password. The cabinet does not keep it.
admin—An isolated deployment on our infrastructure with its own domain, database and runners, set up by our operations team. File a request; we reply by e-mail and here.
Desktop apps signed in to this workspace via cloud login. Revoke a lost or old device to disconnect its access.
Install the app and sign in through your browser — the Space, your role and your data are pulled from the cloud automatically.
Account admission authority
Account-wide consumption and hard ceilings. A hard wall denies new quota-consuming work before it starts.
Every Space under your billing account, its seats and the limits they all share. The shared free pool appears only where it governs.
Box, AI Credits and Infrastructure Units are independent. They are never merged or converted.
Loading…
Loading…
Loading…
A hard cap the Space can never spend past. Set 0 to remove the cap.
Every grant, reservation, settlement, release and refund remains visible.
Bank transfer
The plan changes only after billing support records the transfer and a different finance operator approves it.
Account adjustment
Approved compensation is tied to an already settled order and shown separately from payments and refunds.
Mockarty Desktop
A period key for Mockarty Desktop works on several machines without internet: paste it into every desktop and confirm each machine here with the code it shows.
Benefits ledger
A promotion funds real execution on Mockarty-hosted models; BYOK profiles do not spend Cloud credits.
Service desk
Keep a private case thread tied to this Space. Support access to diagnostics is always separate and time-limited.
Programmatic access for CI, SDKs, and scripts. The plaintext token is shown only once at creation.
Receive mock events at your URL. Payloads are HMAC-signed.
Account access
Link a trusted provider so you can use the same Cloud account without creating a duplicate workspace.
Linking and unlinking require a recent sign-in or your current password or 2FA code.
—
Save these one-time backup codes somewhere safe — each works once if you lose your device:
Let members sign in through your identity provider. Register the URLs below on your IdP, then paste its metadata XML here.
Connect your identity provider (Okta, Entra ID, OneLogin) to auto-provision and deprovision members. The token is shown only once.
Security decisions
Track a security review without exposing the checks that protect your account.
Only the public case reference and review state are shown. Detection signals and thresholds stay sealed.
Data control
See why data is processed, control optional telemetry, and exercise access or deletion rights.
—
A tracked deletion request revokes access after team ownership and legal-retention checks.
Events of the selected Space. Reading the trail requires the owner or admin role there.
Chain integrity OK
Global visibility — operators see every tenant.
Customer care
Consent-safe signal
Only allowlisted dimensions from users with current analytics consent are counted.
Counted events: account created, desktop connected, runtime operation, checkout, support case. A user without analytics consent adds nothing.
Public identity
One audited source for public domains, contacts, legal links and outbound mail identity.
Enable support and set both attachment fields to enable uploads. The storage path is locked after the first accepted file.
Every change requires identity confirmation, an exact revision and an immutable audit record.
Hosted AI economics
Each shared-node profile has its own visible AI-credit burn rate. Customer BYOK profiles and on-prem installations never use this wallet.
Publication requires step-up authentication and an immutable audit record. Existing reservations keep their original rate.
Shared execution
Bind a per-Space runner pool to committed entitlement authority. Bootstrap credentials are revealed once and exchanged for short-lived signed claims.
Changing or rotating a pool requires step-up authentication, exact revision fencing and an immutable audit record.
Identity gateway
Control the identity gateways available on the Cloud sign-in screen. Secrets are write-only, encrypted and versioned by the Cloud control plane.
Saving changes affects every Cloud sign-in screen. Existing sessions are not revoked.
Delivery authority
Configure outbound email, payments and receipt fiscalisation without exposing credentials back to the browser.
Saving rotates an immutable credential version. Fiscal and payment jobs stay pinned to the version selected for their operation.
Admission ledger
Review challenged operations and lift only reversible controls after verifying the customer context.
Select a case to inspect its admission trace.
Evidence is minimized and pseudonymized. Every release requires step-up authentication, a reason, revision fencing, and an audit record.
Dedicated instances
Customers ordered an isolated deployment. Take a request into review, mark it provisioning while operations builds it, then hand over the sign-in address — the requester is told at every step.
Provider evidence
Review signed chargeback outcomes. Two different operators must approve a provider decision.
Provider payloads and customer identity are not exposed. Every decision is generation-fenced, step-up protected and audited.
Bank evidence
Billing support records a reference and document digest. A different finance operator approves the frozen order.
Raw statements are never stored here. Every mutation is step-up protected, generation-fenced and audited.
Money in limbo
A payment the provider left ambiguous, a refund it could not complete, or a receipt it never issued. Somebody is waiting for their money or their document.
Every resolution is step-up confirmed and recorded against the operation generation, so two operators cannot resolve the same incident twice.
Rights that will not settle
The commercial state moved but the derived grant never caught up, so every read answers 409 and the customer has no modules. These have already outlived every automatic retry.
Before the first sale
A market sells only when every step below is in place: approvers, a legal seller, an approved policy for the market, public prices, payment and fiscal connectors, and the two-person market release. Publish in order; the readiness panel names what is still missing.
1
A platform admin appoints a finance approver (sellers, prices) and a privacy counsel (market policies) — two different people. Nobody appoints themselves.
2
3
A privacy counsel publishes the tax and fiscal policy for seller × market. A new revision retires the previous one.
4
One open price per plan × market × currency. Publishing a new price closes the previous one at the new start.
5
The evidence bundle pins the current terms, policy, price and connector versions; a privacy counsel and a finance approver — two different people — approve the gate. Any later change to those artifacts needs a new release.
Promotions and rewards
A campaign is a promotion code that credits a usage wallet. Draft it, activate it, pause or end it; every redemption stays traceable and can be clawed back with a reason.
Immutable ledger
Export seller, currency, tax, refund and fee provenance without customer workload data.
Three-ledger control
Compare authoritative provider readback, fiscal receipts and accounting projections without exposing customer data.
Only stable entity references, amounts and one-way evidence digests are shown. Provider payloads and customer identity remain sealed.
Anonymous usage + error signal from the free/anonymous desktop funnel (install-id keyed, PII-redacted).
Chain integrity OK Export CSV