Account Model

Starbase has a slightly different market model from Deribit. Deribit has a system with main-accounts and sub-accounts. For order entry and drop copy, there is no difference between main-accounts and sub-accounts. Logical grouping of access scopes should be done on a business level. There are, however, two common exceptions: usage of a Prime Broker or a trading firm with silo-ed pods. For this reason, we are introducing two new concepts:

Concept	Description	Mapping to Deribit
Portfolio	Container for positions, funds, and balances across all currencies	1:1 with account (main- or sub-account)
Member	Group of portfolios representing a trading participant	Can span multiple subaccounts under one main account

Members can only be configured from a main account. Subaccounts cannot create or manage Members. Additionally, the Starbase section will only appear in your account panel once your account has been authorized by a Deribit admin.

Member limits

Rate limits are allocated per Member and are shared across all API keys, sessions, and portfolios within that Member. Having more sessions or more portfolios does not increase your rate limits.

See the table below for the Member/Portfolio setup for the three major account types.

Use Case	Description
Directly onboarded client	These clients are set up with exactly one Member and will not be granted additional Members. All portfolios/sub-accounts fall under this single Member.
Prime Broker clients	Clients of Prime Brokers can request their Prime Broker to set up their subaccounts as a single Member. This ensures that clients of a Prime Broker can trade completely independently of other clients of the same Prime Broker. Any new portfolios/sub-accounts will need to be added manually and by request of the Prime Broker.
Pod-based trading firms	Trading firms with multiple trading pods that act independently can request each pod to be set up as a Member. This allows pods to trade completely independently from other pods. Any new portfolio/sub-account will not immediately be part of a Member grouping.

Members should reflect genuine business-level separation — for example, competing trading desks or independent prime broker end-clients. Multi-member setups are not allocated higher rate limits than single-member setups. An example of a justified multi-member setup is a Prime Broker with two distinct, independent market makers as end clients.