What oppen is
oppen is a local-first perpetuals terminal built for agentic trading. It runs on your machine. It is not a hosted service, not an exchange, not a broker, not a custodian, and not a decentralised exchange.
We never take possession of your funds, your private keys or your positions. We cannot execute a trade for you, cannot move your money, and cannot recover an account, because there is no account and we hold nothing.
Status: pre-alpha
There is no public release. The software is under construction and described here as it is intended to work, not as a finished product. v1 targets Hyperliquid only and defaults to testnet. Interfaces, guardrails and behaviour will change.
Do not treat anything on this site as a commitment to ship a particular feature on a particular date.
Licence and trademark
The source is licensed under the Apache License 2.0, and opens at launch, Q4 2026. Contributions require a contributor licence agreement.
"oppen" and "OPPEN" are trademarks. You may fork and modify the code freely under the licence. You may not distribute a fork under the oppen name. This is not branding vanity: the safety claims made here describe one particular build with particular invariants, and a fork that removes the guardrail check while keeping the name would be a safety problem for users, not just a naming dispute.
No warranty, and what that means here
The software is provided "as is", without warranty of any kind, express or implied, as set out in the Apache License 2.0. To the maximum extent permitted by law, the contributors are not liable for any loss arising from your use of it, including trading losses.
Stated plainly, because the licence language is easy to skim past: if oppen has a bug and it costs you money, that loss is yours. That is the deal with free software that signs financial transactions. It is also why the source is open, why the guardrails are enforced in a small auditable core, and why the default is testnet.
Trading risk
Perpetual futures are leveraged instruments. You can lose more than you expect, quickly, and positions can be liquidated automatically.
- Nothing here is financial advice. We are not your broker, adviser or fiduciary. oppen ships no strategy, no signals and no default agent behaviour. What your agent decides to do is your responsibility.
- Guardrails bound loss to the limits you set; they do not prevent loss. An operator who sets a 50% circuit breaker has authorised a 50% loss.
- oppen does not protect you from venue risk. Oracle failure, forced deleveraging, protocol exploit and chain-level failure are outside its control.
- oppen does not protect a compromised machine. An attacker with code execution and keychain access on your device can trade within your guardrails. The mitigation is that the loss is bounded and funds cannot be withdrawn, not that the attack is impossible.
Your responsibilities
- Keeping your machine, your operating system keychain and your wallet secure.
- Choosing guardrail values you can actually afford to lose.
- Reviewing what your agent does. The decision ledger exists to be read.
- Complying with the law where you live, including any restriction on trading perpetual futures or derivatives. Availability of this software is not a representation that using it is lawful in your jurisdiction.
Builder fee
Official builds attach a builder code to orders. The fee is small, disclosed in the project documentation, and bounded by a maximum rate that you sign once during setup. oppen cannot exceed that cap without a new signature from your wallet. The rate is visible in the console and recorded per order in the ledger.
This website
The site is provided for information. We try to keep it accurate and will correct it when it is not, but we do not warrant that it is complete or current. Any figure describing performance is a design target unless explicitly labelled as a measurement.
Changes
We may update these terms. The date at the top changes when we do, and material changes will be noted in the project's release notes.
Contact
[email protected]. Security reports go to /.well-known/security.txt.
These terms are published by the oppen contributors. A governing-law clause and the responsible legal entity will be added before the first public release. This document is not legal advice.