Invite-only access
Your QC account
Manage your team, API keys and jobs. Reports and evidence are accessed in your tenant environment.
Google sign-in
Checking sign-in configuration…
Accept a team invitation
Save the individual console key shown once below. You can also use Google after accepting.
Save this credential
Shown once. Store it securely before closing.
Your quality operations, from submission to decision.
API keys
Keys are shown once, expire automatically and stop working when revoked or their owner loses access.
QUALITY OPERATIONS
Jobs & reports
Follow progress, review findings and configure the report you share.
Input files stay in your connected storage. Processing runs in your isolated environment; reports open separately when ready.
Start a QC run
Advanced JSON request
Use the documented JSON request. Include an idempotency key to retry safely.
Technical details
Team
Invitations expire in seven days. Share the one-time token through your secure channel.
Pending invitations
Request activity
Only route templates, actor IDs, timestamps, response codes and timings are recorded. Request contents are excluded.
METERING
Usage & run ledger
First runs and reruns, with a traceable record for every job.
How hours are counted
Measured input duration comes from the completed QC report. Reruns use the same immutable source manifest set or an explicit retry. Automatic worker attempts and duplicate idempotent requests do not create additional usage entries. Changed source manifests require review when comparing runs.
Missing measurements are shown as unknown. Dataset orchestration jobs are identified separately until they have trusted duration receipts. This page shows usage. Pricing and payment terms follow your agreement with Oru’el; these totals are not an invoice.
Dates select jobs submitted in the UTC period. These totals can increase as those jobs finish. Input duration is the engine’s dataset duration, and does not mean every check covered every frame.