01
Scope and common rules
This annex applies to the relevant Laintas Compute functions together with the Platform Terms, Privacy Policy, Data Use Notice and Billing and Refund Policy. It supplements or overrides general terms only on its stated product matters. Mandatory law and valid individually negotiated agreements take priority. The version expressly provided and validly accepted at purchase or use applies; a web update does not automatically change existing orders.
02
Own devices, traffic and calls
Models execute on your device or chosen runtime while the gateway relays requests and answers and records bytes, timing, tokens and status metadata. This path has no Laintas per-token inference charge; membership or purchased traffic applies. Exhaustion, offline devices or unavailable allowance checks refuse or pause calls without a silent paid-model fallback. Offline status does not revoke credentials; remove the device and local credentials to end access. Power, hardware, connectivity and chosen runtime costs follow their respective agreements.
03
Rental price, start and settlement
Rentals use account balance, not membership inference allowance. The GPU, hourly rate and fixed-duration or open-ended mode are shown at ordering. Current metering starts at started_at when the service successfully connects and marks the machine running, not merely on order submission. Subsequent model download and loading occupy billable time. Settlement is generally every ten minutes against actual elapsed time with a final cent-rounded reconciliation, not an automatic full ten-minute minimum per started interval. Any separately displayed fixed fee also needs confirmation. Destruction retries do not extend the user billing cutoff beyond the stop request.
04
Deployment failure, faults and review
Allocation failure or startup timeout before a billable running state is not normal runtime. After readiness, incompatible models or failed download/loading may still occupy rental time; stop and request cause-based review rather than assuming all rental time becomes free. Laintas-attributable non-delivery, duplicate time or misbilling requires correction and lawful remedy. Upstream faults are assessed by timing, records, order and duties, not an automatic third-party refund exclusion.
05
Insufficient funds, ending and destruction
Expiry, stopping, insufficient funds, safety action or upstream interruption can stop and destroy a machine. Open-ended use is not unlimited credit; insufficient balance for the next settlement interval can trigger reclamation. Machines and disks are temporary and data is not retained after reclamation. Back up during the rental and do not use it as sole storage. Export before ending, without excluding liability for the platform’s own actionable fault. Protect SSH private keys.
06
Devices, infrastructure, models and licences
Rental infrastructure may use Lium, Vast.ai or the providers actually enabled for the order. Location follows selected-machine and available order information; underlying infrastructure may be controlled by the supplier or host. You need authority over devices and model use and must comply with model, runtime, download-source and infrastructure licences and use restrictions. Downloadability does not imply resale rights. Installers may install engines, download models or enable startup as chosen; verify sources and device permissions. Private-model access tokens are limited to authorised purposes.
07
Start, ten-minute settlement and stop cutoff
Current rental time starts after SSH connects successfully and the instance enters running state. Model downloads, loading and preparation then occupy billable time; charging does not wait for the first successful inference. Settlement ordinarily posts elapsed time every ten minutes and reconciles actual remaining occupancy at end, rounding to cents under ledger precision, without a ten-minute minimum per start. A successfully recorded stop request uses stop_requested_at or the relevant end time as the user cutoff. Destruction retries must not extend charges beyond that cutoff. Request a start, cutoff and debit reconciliation by rental ID if states differ.
08
Capacity, estimates and additional costs
Check GPU, memory, disk, region, availability and hourly rate at confirmation. A listing estimate is not a promise of fixed availability indefinitely. Allocation failing before normal billing state should not incur normal runtime charges. Incompatibility, slow downloads and configuration failure after running depend on occupied time, cause and delivery promises. Separately billed storage, network or other items require prior disclosure and authority; a GPU listing neither includes everything for free nor authorises unlimited extras. Rate changes must not arbitrarily reprice confirmed elapsed periods.
09
Machine data, disconnection and destruction
Rental disks and memory are not long-term Laintas Storage. Models, logs, output, keys and caches may be lost on destruction; export important results before stopping. Closing a browser, losing SSH or idle inference ordinarily does not stop rental. Insufficient balance, security shutdown and infrastructure failure can interrupt work; check instance state and final settlement. Laintas can clean and destroy controlled instance resources but does not promise instant physical erasure of every host medium, snapshot or external backup. Confirm providers and deletion arrangements before sensitive use; destruction is not a universal zero-remanence guarantee.
10
Own-machine connection and model licensing
Connect only devices you lawfully control and within organisational network rules. Protect device tokens, management ports and runtime accounts. Relaying, control plane and local inference are distinct; no model-token charge for own-machine calls does not remove traffic, power, model-licence or other costs. Downloads and inference must respect model commercial-use, regional and redistribution conditions; technical compatibility is not a licence grant. Offline devices or exhausted traffic should fail or wait according to state, without silently switching to a paid model.