Each engagement is defined by a written scope (a short Statement of Work) agreed before any deposit is collected. Opsline delivers exactly what's specified there. Anything outside that scope is quoted and billed separately.
Each package includes one round of revisions within the original scope. Additional rounds or scope changes are quoted separately.
Delivery windows quoted on the pricing page are estimates based on typical builds. Any delay is communicated as soon as it's known.
On final payment, you own the delivered code, configuration, and any credentials created specifically for your build, outright. Opsline retains the right to reuse general-purpose components and patterns — not anything specific to your project — in future work.
Opsline builds and configures the agent. It doesn't operate or guarantee the uptime, policies, or behavior of third-party platforms the agent runs on — Discord, Telegram, blockchain networks, RPC providers, and similar. Ongoing maintenance is available separately; it isn't included by default.
Opsline's liability for any engagement is limited to the fees paid for that engagement. Opsline isn't liable for indirect, consequential, or lost-profit damages, or for losses arising from third-party platform outages, chain congestion, or your team's use of the delivered agent.
Anything you share about your project that isn't already public stays confidential.
Either side can end an engagement before it starts, with no obligation. Once started, the payment section above applies.