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.
The Oppen team does not take custody of funds or receive account-owner private keys. The local application uses approved agent-wallet keys to sign venue actions. Funds and positions remain in your venue accounts. We cannot recover your wallet or its keys.
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
oppen is open core. The trusted computing base — signing, guardrails, the ledger and the agent gateway — is licensed under the Apache License 2.0 and is planned for public source publication at launch. The operator console and the layers above it are covered by the oppen Commercial Source License: you may read them, build them, and run and trade with your own build, including for profit and on behalf of a firm you work for, with no separate agreement; you may not redistribute or resell them. Contributions to either half require a contributor licence agreement.
"oppen" and "OPPEN" are trademarks. You may fork and modify the core freely under the Apache 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. Public source access is planned for launch. The system remains under validation and defaults to 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 do not guarantee a maximum loss. Loss triggers react to observed conditions. Gaps, fees, funding, liquidation and delayed exits can take losses beyond the configured threshold. Halting new orders does not close positions.
- 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 who extracts a signing key can bypass local guardrails. The venue still applies that key's permissions; compromise of your account-owner wallet may also expose withdrawal authority. Multiple keys on one host may expose multiple funded accounts.
Your responsibilities
- Keeping your machine, your operating system keychain and your wallet secure.
- Allocating only capital you can afford to lose and understanding that a guardrail trigger is not a guaranteed loss ceiling.
- 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 are intended to attach a builder code to eligible orders. On Hyperliquid, the account owner approves a maximum fee for the builder. Each applicable account needs its own approval. The effective rate should be reviewed before use; venue fees, funding and model-provider charges are separate. The release must disclose its fee behavior and approval requirements.
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
legal@oppen.xyz. 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.