These pages describe the current Oplut website, account surfaces, CLI/runtime, device evidence sync, catalog, and planned product direction reflected in the public codebase.
What Oplut is
Oplut provides software for physical hardware visibility: a CLI/runtime, SDK and API surfaces, setup catalog, device registry, dashboard, and baseline/check workflows. The product is built around a local-first loop: install locally, capture the known-good state, check what changed, and sync compact evidence when useful.
Accounts and device access
You are responsible for the accuracy of account information, the security of your password, account sessions, API keys, and device authorization codes.
A linked device may be associated with a device fingerprint, device name, project label, board, OS, architecture, peripherals, and service status while it remains connected to your account.
Device limits, dashboard access, API access, and cloud sync features may depend on your plan or subscription status.
Setup and hardware operations
Oplut setup workflows may install packages, write configuration files, create services, restart services, or request elevated permissions when you explicitly run them.
You are responsible for reviewing setup steps before execution and for using Oplut only on hardware, systems, and networks you are allowed to manage.
Oplut may infer likely hardware or wiring issues from observable symptoms, but it cannot directly see physical wiring and should not be treated as a replacement for safe inspection.
Evidence you may sync
Oplut is designed to store compact operational evidence by default. This can include setup results, config IDs and hashes, service state, baseline metrics, current-vs-baseline changes, component summaries, calibration metadata, health observations, recommendations, failure classes, provenance summaries, and trust status.
Data you should not upload casually
Do not upload secrets, access tokens, private keys, passwords, unsafe instructions, or material you do not have the right to submit.
Raw camera frames, video, audio, full sensor logs, full calibration image sets, large diagnostic bundles, and private project files should use an explicit artifact workflow and opt-in.
Community configs, comments, reviews, reports, and public catalog contributions may be visible to other users when submitted to public surfaces.
Community catalog and contributions
Public hardware configs are intended to be browsable, runnable, and contributable. When you submit public content, you grant Oplut permission to host, display, modify for formatting or safety, and use it to operate and improve the catalog. Private or enterprise setup material should only be submitted through surfaces intended for private use.
Billing
Paid plans may unlock additional device capacity, dashboard features, baseline/check history, SDK/API access, team workflows, or lifecycle intelligence. Payments and subscription management are handled through Stripe. Oplut stores Stripe customer and subscription identifiers, not full card numbers.
Ownership and product learning
You keep ownership of your hardware, projects, private files, and the evidence you submit.
You allow Oplut to process submitted data to provide the service, support devices, secure accounts, debug failures, improve setup paths, and build aggregate hardware intelligence.
Oplut may use de-identified or aggregated operational evidence to understand hardware behavior, failure patterns, config reliability, and population-level trends.
Safety and acceptable use
Do not use Oplut to operate unsafe systems, evade access controls, attack services, violate laws, collect data without rights or consent, or create setup instructions that would damage hardware or put people at risk. You are responsible for validating any command or recommendation before using it on real equipment.
Availability and changes
Oplut is evolving quickly. Planned features such as deeper calibration lineage, cross-sensor drift detection, team workflows, population intelligence, and broader SDK contracts may change before public release. We may update these terms as the product changes.
Disclaimers
Oplut is provided as available and without guarantees that every setup, baseline, diagnosis, recommendation, or hardware inference will be complete or error-free. Hardware work carries real-world risk, and Oplut outputs should be reviewed by a qualified person before action is taken.
Contact
Questions about these terms can be sent to hello@oplut.com.
The short version: use Oplut on hardware you control, keep sensitive raw data out of default sync paths, review actions before running them, and treat baseline evidence as a tool for better physical judgment rather than an automatic safety guarantee.