AccezzCompute private beta
Use compute.
Keep control.
Approved requesters submit supported work while approved GPU providers control when and how their computers are available.
Getting started
Apply for the private beta, verify your email, wait for account approval, then sign in to the portal for your role. Controls appear only when your account and the service catalog permit them.
Request compute
Submit supported work, monitor lifecycle and retrieve verified results from the console or API.
Open Compute Console →Provide capacity
Connect approved hardware, define safe operating boundaries and review activity.
Open Provider Console →Capability status
- Console: interactive controls backed by an approved browser contract.
- API: implemented service capability currently integrated through the documented API, not a browser workflow.
- Approval: governed capability requiring authorization or launch evidence.
- Blocked API: no approved browser contract exists; the interface does not simulate one.
For compute requesters
- Open the Compute Console and review the effective workload catalog.
- For private inference, upload a GGUF model and wait for verification before registration.
- Submit supported work and follow its status. Charges settle only according to the published lifecycle.
- Create narrowly scoped API keys for server-side integration; copy each secret once.
- Use the API protocol for API-only programme workloads until a browser contract is approved.
Never put API keys in public browser code, mobile applications, repositories or screenshots.
For GPU providers
- After approval, download and verify the Worker Application.
- Generate a one-time enrollment code and enter it on the device.
- Choose availability, thermal limits, schedules, cache policy and allowed workload categories.
- Confirm readiness in the Worker and Provider Console.
- Review privacy-safe job history and distinguish estimates from settled earnings.
Privacy and trust
- Each role sees only information necessary for its task.
- Requesters do not receive provider device or network identities.
- Providers do not receive requester identity or private account information.
- Unsupported, adapter-gated and production-only capabilities are labelled instead of being presented as available.
- Secrets and private payloads must not be placed in URLs, logs or support bundles.
Support
Include the safe job reference or device display name shown in your console. Never send passwords, API keys, model payloads, enrollment codes or infrastructure details.