OpalSpan: subscription terms
Version: subscription-terms-en-2026-10-06-v11. Offer: 2026-10-04-dkk. Language: English.
Seller and contact
Ready IT ApS, CVR 38769383, Danish VAT number DK38769383. c/o Matt Luccas Phaure Jensen, Viften 18, 1. 1, 2670 Greve, Denmark. Email: contact@readyit.dk. Telephone: +45 22 76 54 06. Use these contact details for questions, complaints, cancellation and withdrawal notices.
Service and price
OpalSpan provides AI-driven device support, remote technical access and customer/case coordination. The order identifies the available features, supported Windows/Linux systems and versions, material technical requirements, commencement and any access limits. Planned features are not included. The remote-access service uses the native encrypted relay. A supported client, internet connectivity and authority to access the selected systems are needed. Windows x64 and Linux x64 are supported platform families; macOS support is not part of this offer.
Where the order includes hosted OpalSpan Mech, it can investigate supported devices, carry out authorised software work and record the result. This may include commands and file changes on authorised systems. AI responses and actions can be incorrect, and a repair is not guaranteed. Mech may use relevant material across cases in the same authorised workspace; separate chats do not isolate that material. The privacy notice explains the personal-data handling.
Selected monthly DKK offer
Amounts exclude applicable VAT, per workspace per month. The order and Stripe Checkout show applicable tax and the amount to pay before commitment.
| Free | Shop | Business | Fleet | |
|---|---|---|---|---|
| DKK/month | 0 | 800 | 2,600 | 6,000 |
| Concurrently enrolled devices | 5 | 25 | 150 | 500 |
| Included monthly work sessions | 25 | 300 | 1,500 | 5,000 |
| Included monthly AI credits | 250 | 2,500 | 10,000 | 20,000 |
| Human members | 1 | No per-person charge | No per-person charge | No per-person charge |
| Executing hosted Mech runs | 1 | 5 | 10 | 20 |
All paid plans include ordinary authorized CLI and Mech access, device work, cases, customer records and security controls. Agent processes are not human members. Roles, device authority and consent still apply. Standard plans and capacity add-ons are monthly self-service purchases; no compulsory call, email, annual commitment or bespoke procurement process. Enterprise is for genuinely different contractual, procurement or operational requirements, not an automatic route for more devices. Cases are unlimited. Paid support remains email support; Free support is documentation/community, without a response-time guarantee.
This DKK generation does not redefine an existing EUR/USD order. Its accepted prices, capacities, credits and agreement generation remain applicable until a separately accepted prospective change. These terms specify no new EUR/USD Fleet, device-block or additional-session tariff.
Deliberately purchased capacity
Every paid plan may explicitly purchase blocks of 25 additional concurrently enrolled-device slots for DKK 100 per month per block excluding VAT. The purchase and its first prorated invoice are shown before payment. Capacity becomes available only after verified payment. Discovery and enrollment attempts never purchase a block. Offline enrolled devices count. Devices which are no longer enrolled do not occupy slots merely because historical records remain.
Each add-on's paid period, ordinary cancellation and renewal are inspectable in billing. Cancellation stops future renewal and preserves already-paid capacity through its paid end. No devices or history are deleted when capacity decreases; authorization and new admissions are rechecked.
Actual device-work sessions
A session covers actual authorized device work in one workspace on one device. It begins when the device accepts an on-demand operation. Background monitoring, idle connections, transport keepalives, administration and reads of stored results neither start nor extend a session. A running operation remains work even without output. The next actual work after at least 60 minutes of inactivity, or work continuing into a new date in the workspace billing timezone, starts another session. Concurrent/retried operations, technicians, tasks, cases, models, conversations and Automation runs share the applicable device-work window. Changing a plan creates no work-session identity or reset.
Free requires an upgrade after its allowance. Each additional session costs DKK 4 on Shop and DKK 3 on Business excluding VAT. Fleet is graduated: the first 5,000 monthly sessions are included; sessions 5,001–20,000 cost DKK 1.50 each; only sessions above 20,000 cost DKK 1 each. Crossing a band never reprices earlier units. Allowances reset monthly without rollover; past accounting remains fixed.
Explicit monetary spending controls
The subscription and deliberately purchased capacity establish the default recurring commitment. Paid-session overage has a default monetary budget of zero. An authorized human may confirm an exact workspace, member or run limit. The confirmation identifies the workspace, target scope, amount, tariff, expiry and actual device target set where applicable. Its aggregate potential work-session cost is shown separately from the AI budget. A per-device maximum is not a fleet maximum; an AI balance is not a paid-session cap.
The limit includes accepted charges and in-flight exposure. An old conversation message, model-supplied confirmation flag or saved Automation does not renew charge authority. Already-dispatched work crossing an idle/date boundary may continue within its existing execution limits at OpalSpan's expense where a new charge is unauthorized; that continuation is not later debt. Further unauthorized chargeable operations are refused, not silently billed or blindly terminated. Billing permits no otherwise unauthorized device access.
AI credits
One AI credit represents USD 0.01 of customer-priced usage. Fractional usage is accounted for exactly. The same customer rate schedule applies across plans; included credits are used first and expire monthly, while purchased credits do not expire. Credits and included sessions do not promise completed repairs. Your balance shows a useful retail monetary equivalent. Top-ups remain explicit, customer-entered and separate. No automatic refill, new credit currency or additional top-up/wake/prompt/conversation fee is added. Positive purchased or prorated grants use the existing customer-favour rounding up to a whole AI credit; fractional usage remains exact. A new Mech request needs usable credits. If an already-running request exhausts them, Ready IT covers the unheld excess; there is no negative balance or later recovery of that excess. One bounded tool-free wrap-up may explain the outcome, but further charged work requires usable credits. Already-dispatched device commands retain their existing execution limits; exhausted AI credit is not permission to cancel or broaden them. The separate Quick-only fallback allowance is 200/13 credits (approximately 15.384615), requiring explicit consent rather than an automatic model switch. Included allowances expire monthly; non-expiring purchased credits are unchanged. A successful hosted analysis of one selected conversation file costs 5 AI credits plus usual model-token usage; failed/unmetered attempts and internal retries do not create another session fee.
Proration and retained customer terms
Stripe quotes and invoices the actual initial or upgrade charge. The calendar renewal date stays unchanged; upgrades are invoiced immediately and lower paid plans take effect at the paid-period boundary. Paid entitlements require a verified paid invoice. New DKK first purchases, including Free→paid, activate immediately after verified payment rather than waiting for the next month. Full paid device capacity and the paid monthly session allowance apply immediately; earlier sessions still count. The initial included AI grant and upgrade allowance differences use the existing remaining-month fraction with customer-favour whole-credit rounding. Already-issued Free grants are not revoked, purchased credits are unchanged, and usage does not reset. Full-month plan comparisons are not mid-month invoice quotes. Accepted existing terms and invoices stay applicable until a legitimate, explicitly accepted prospective change; public updates never rewrite history.
Automations and device-health monitoring
Where included by the workspace's applicable accepted offer and enabled within its lawful scope, an Automation asks Mech to start authorised work on an explicit schedule or deterministic device-health alert. You choose its enrolled devices, objective, IANA timezone and recurrence or alert rule, model/reasoning, permitted action scope and whole-run AI-credit cap. Normal authorised investigation and software actions are available; observation-only work is optional, not a compulsory pilot. A repair or complete alert coverage is not guaranteed. Work hours are advisory and do not grant device authority.
One Automation has one persistent Mech conversation, created when needed. Each wake-up is an individual run with its trigger/configuration snapshot, actual targets, current owner/authority/model, budgets, status, accounting and observed result. There is no new conversation per wake or device. Selected instructions and relevant recent results supply bounded model context; keeping history does not mean replaying all of it. A stored configuration, old history or approved budget grants no new role, device-user consent, commercial charge or permission to repeat an uncertain operation. Admission and resumed model/tool dispatch recheck current member/device/scope, provider and budget authority.
| Plan | Active Automations | Minimum recurring interval | Executing hosted runs |
|---|---|---|---|
| Free | 2 | 24 hours | 1 |
| Shop | 20 | 1 hour | 5 |
| Business | 100 | 1 hour | 10 |
| Fleet | 500 | 1 hour | 20 |
These limits apply only to the exact selected commercial generation. Missing fields, publication or continued use do not migrate an earlier order. A multi- device object counts once; paused objects and completed one-time schedules use no active slot. Saved conversations and person/provider waits use no executing slot. Alert sustain/rearm/cooldown/deduplication and daily-storm limits are independent of the minimum recurring interval.
Schedules use explicit local wall-clock time in an IANA timezone. A daylight- saving gap maps to the first valid instant after it; a repeated time fires once at the earlier instant. Due work queues only within its configured start window. Idempotent claims and overlap policy avoid replaying active work. After missed occurrences, at most the latest still within the start window runs; older ones are recorded as missed. Resume waits for the next occurrence, not a paused backlog. Offline devices, budgets, authority, capacity and interruption can delay, skip or interrupt work; stale telemetry cannot generate a catch-up storm.
Authorised Agent CLI, Mech and web controls configure, inspect, pause, resume, change/delete the Automation, inspect results, cancel an exact run, answer an exact question or explicitly continue in the same conversation. Cancellation is not guaranteed reversal of a device-accepted action; inspect operation evidence before intentional retry. Authority loss pauses work; an authorised Admin must explicitly adopt it before using another member's authority. Waiting performs no inference; reentry rechecks scope/budgets/execution capacity.
There is no wake/prompt/conversation fee. The same fractional retail AI credits, included-first monthly expiry and non-expiring purchased credits apply. The whole-target-set run cap, available credits and member limit are never exceeded by customer charge. Admission needs usable credits above zero, not an upfront full-cap debit. Ready IT covers bounded final excess without later recovery, allows one tool-free wrap-up and stops further model/tool work. Unknown usage holds bounded exposure without a guessed customer debit. Original exemptions remain. A wake alone consumes no device-work session; actual device-accepted/ ongoing work shares the sixty-minute and billing-date unit defined above. Whole-run monetary session authority defaults zero and derives only from the exact immutable human-confirmed configuration/terms, separately from AI credits. Workspace/member/run accepted plus in-flight limits remain binding. No new wallet, tariff, automatic purchase or refill is authorised by Automation.
Lightweight enrolled-device health
The default health-first-slice-v1 profile contains exactly eight signal
families: presence, volume free-space percentage, free bytes, system-volume
fill trend, new crash-record indication, unexpected-reboot indication, optional
disk-warning code and thermal-pressure state. Existing first-slice instructions
and consent are not instructions or consent for additional fields.
The separately selectable health-catalogue-v1 profile includes that first
slice and only these additional coarse/numeric fields: OS uptime; physical
memory available percentage, memory commit percentage, Linux memory-stall
percentage or native Mac memory-pressure level where available; resource-
exhaustion counts; free inode percentage and system-filesystem read-only state;
supported update-reboot requirement, age of an actually reported successful
update and fixed update-failure counts; registered antivirus aggregate health
or Gatekeeper assessment-control state; fixed service-failure counts or the
systemd failed-unit count; battery full/design capacity percentage; and fixed
hardware-error and system-error counts. The privacy notice and instructions
specify the exact IDs, sources, OS gaps and bounds. This is not patch compliance,
a malware-free assessment, an RTP guarantee or a complete health diagnosis.
Evidence and availability differ by OS. Missing/failed/stale readings are explicit, not healthy zeros. Windows/Linux are supported platform families; separately supplied macOS software remains technical preview without supported- platform, Apple-signing/notarization or physical-acceptance claims in this offer. No raw log/report/file content, usernames, sign-in addresses, threat names, applications/software inventory, serials, network names, paths, commands or environment variables are collected by either background profile. Hashes and device linkage can be personal data; hashing is not anonymity.
Small metadata/deltas and periodic keyframes use the existing authenticated encrypted enrolled-device channel. Collection/deterministic evaluation uses no AI credits or device-work session. Only necessary signal/threshold/context enters a separately authorised Mech run under existing accounting; deeper diagnostics still require explicit sections/profiles. Rescue is excluded. Bounds and cadence do not promise exhaustive or instantaneous detection.
Additional collection remains off/unselected unless its own exact published version/hash, original holder's attributable target/profile-bound instruction, device-user consent for that exact profile/notice or evidenced necessity for monitoring expressly requested by that user, native capability and explicit per-device/selected-device profile choice all hold. Purchase, publication, membership, enrolment, an old contract, silence or an opt-out notice supplies none of that evidence. A broader instruction neither replaces first-slice instructions for other devices nor changes the first-slice future-enrolment default. Future enrolments never automatically select the additional profile.
The device user may withdraw consent and use native local opt-out. An agent or workspace default cannot override it. Removing a local veto creates no consent. Off/downgrade clears unsent additional records and fences in-flight results; a stopped computer cannot be remotely wiped. Transfer retires old workspace telemetry and authority rather than carrying consent into another workspace.
Historical readings expire seven days from original observation; events/alerts thirty days from recorded occurrence. Latest non-event state remains separate, timestamped and potentially stale while enrolled. The local queue is at most 64 batches/256KiB, expiring after seven days from original sample age during operation or next startup and clearing on acknowledgement/off. Row/byte limits may prune earlier. Cases, conversations, authority, financial/contract and recovery records retain their separate unchanged purposes and retention.
Separately requested resource monitoring
health-resources-v1 is an independent optional scope: the unchanged eight
first-slice IDs, uptime and the four existing memory IDs, plus aggregate CPU
utilization, up to three reported OS-sensor temperatures and dedicated GPU
memory usage/capacity/utilization. It excludes the catalogue's other fields.
The v7 privacy notice and processing instructions enumerate exact IDs,
native sources, platform gaps and bounds. Utilization is not reclaim pressure;
reported temperature is not necessarily CPU die temperature. macOS remains a
technical preview under this unchanged offer.
The independent v11/v7 publication, explicit profile selection and native0.22 capability do not migrate earlier device grants, orders, tariffs or rights. Resources and catalogue scopes are siblings; neither authorizes the other. Existing cadence, byte/row limits, retention, providers, local opt-out and separately authorized deeper-work/financial boundaries remain unchanged.
Authenticated requested monitoring
An explicit monitoring request from the signed-in authorised technician is the service action and its attributed request evidence. Within the actual permitted workspace/device scope, the service fills the required purpose/capacity, published profile/document binding and current revisions and records the prospective instruction and requested-service necessity. Mech trusts that technician request and attempts the permitted command; it does not ask the person to prove their general authority, complete a personal questionnaire, find a separate consent package or approve the same requested monitoring again.
This service-owned evidence is not a fabricated assertion that an unrelated person gave consent. The responsible customer/technician remains responsible for applicable organisation/employee notices and upstream-controller instructions. Existing attributed personal-consent/withdrawal routes remain available where used. Actual server-enforced permission, target, publication, native-capability and local-opt-out refusals remain boundaries. Removal of a local veto never supplies a monitoring request or new grant. Explicit additional-profile selection is required; older grants are not silently migrated. Genuine unattended-work, financial and native-access decisions retain their separate unchanged controls.
Existing orders and feature-only acceptance
This adds only prospectively requested scheduling/monitoring scope, not a silent amendment or migration of an earlier order. Complete original copies, holder identity, prices, tariff/allowance snapshots, credits, exemptions, usage and statutory rights remain intact. Existing holders must affirmatively accept the specific additional scope and exact version/hash/target-bound instruction, with material changes shown and fixed copies available. Device-user consent is separate. That instruction buys no plan, migrates no tariff, resets no usage and grants no Admin rights. An older commercial generation without Automation stays unavailable until a separately accepted applicable order; no foreign tariff is invented or existing economic right removed.
Email is not activated by this package
Results/questions remain accessible in the private Mech conversation and client views. This schedule/monitoring package does not activate Automation notifications or Mech critical email, select a mail provider/purpose, grant mailbox access or approve a real send. Existing contact and contract/rights confirmations remain within their original scope. Future critical-member mail needs separate actual provider-purpose/retention, recipient authority/preferences and exact applicable human send confirmation. Mail is not a prerequisite for independently authorised scheduling/monitoring.
Ordering and contract copies
You select a plan in OpalSpan and continue directly to Stripe-hosted Checkout. Checkout collects the contracting name, receipt email and applicable billing and tax details. OpalSpan treats an order with business details as commercial and one without them as personal or household use. This product default does not decide whether someone has legal consumer rights, authority to act for a business or a particular data-protection role. Review the offer and linked agreement documents before paying.
For an existing workspace, the purchaser must have the required workspace authority. A new customer may pay before creating or signing into an OpalSpan account. Access to the purchased workspace follows payment verification, delivery of the contract copies and secure identity/onboarding checks through Auth0. A Checkout email address or a payment-return URL alone does not grant access to an existing account or workspace.
Stripe's single acceptance control links the applicable subscription terms, consumer cancellation and withdrawal rights, privacy notice and, for native business orders, the processing agreement and instructions. Its concise label includes the express immediate-service request where consumer rights apply. OpalSpan records the native acceptance, document versions and product defaults; it does not represent those defaults as separate customer declarations.
Payment takes place in Stripe-hosted Checkout. Review and correct your details before confirming payment. If the plan, currency or other OpalSpan order details are wrong, leave Checkout without paying and return to OpalSpan to correct the order; do not pay an incorrect order. The order and Checkout show the actual offer/version, available payment method, supported buyer location, applicable tax-inclusive consumer total or calculation method, initial payment, start date and recurring charge before you commit to payment.
These contract documents and this acceptance are in English. You can save and reproduce the supplied documents. The contract confirmation supplies the accepted order information and fixed document copies on a durable medium, including the receipt email you provide, before service begins. Closing the browser does not cancel a completed payment or remove the order; use the verified access/recovery route or contact Ready IT for help. A later login-email change does not transfer the subscription or rewrite the contracting party. OpalSpan retains the versioned agreement record and provides the original contracting holder with private links to the exact accepted document copies. Contact contact@readyit.dk if you need your contract copy or help locating it. A later change to public information does not replace the copies applicable to your order.
Where enabled for your subscription, Stripe Customer Portal provides invoices, payment methods, billing details and subscription-management actions. OpalSpan shows the available entry points; an authorised workspace Admin may use the plan-change flow. Stripe presents the financial effect before you confirm. The original contracting holder's Contract rights and records route remains available after workspace membership is removed, including the applicable period-end cancellation route. It does not grant workspace-administration rights. Stripe supplies invoices and payment receipts; OpalSpan supplies the separate contract and rights records.
Billing and renewal
The selected paid subscription charges the displayed prorated price for the remainder of the first month and renews monthly on the 1st at 00:00 UTC. The initial paid main-credit allowance uses the same remaining-month fraction. Checkout shows the resulting first payment before you pay. The offer identifies the full-month credit allowance and the same remaining-month proration basis. No new paid monthly allowance is granted without reconciled payment.
There is no minimum commitment beyond the current paid period. Ordinary cancellation stops the next renewal; already-paid access lasts through that period. Where paid-plan changes are offered, an upgrade takes effect only after verified payment of the additional prorated charge. The additional included main-credit allowance uses the same remaining-month fraction of the allowance difference; used credits and fallback allowances do not reset. A lower paid plan takes effect at renewal, not by removing the current paid period. Plan changes preserve the renewal date and do not themselves create an automatic current-period refund. Stripe calculates and presents the applicable charge. The separate subscription cancellation and withdrawal document explains cancellation, consumer withdrawal and repayment.
Failed renewal gives seven days' grace without a new paid monthly credit grant unless payment is reconciled. If the renewal remains unpaid when grace ends, the workspace returns to Free. This preserves records and purchased credits; it is not permission to delete customer data or uninstall devices. Where the workspace exceeds Free capacity, Admin/recovery access is preserved and the Admin selects the active humans and devices within that capacity.
Consumers: defects, remedies and complaints
Mandatory rules on defects in the Danish Sale of Goods Act apply where the purchase is covered. Applicable rights to remedy, price reduction, termination, repayment and redemption of purchased electronic value are not excluded. Starting AI use is not a blanket waiver of consumer rights.
Contact contact@readyit.dk with a complaint. If it is not resolved, eligible consumer complaints may be submitted to Maeglingsteamet for Forbrugerklager, Naevnenes Hus, Toldboden 2, 8800 Viborg, through https://naevneneshus.dk/. Its jurisdiction and admissibility conditions apply.