Question 1

How do I get access to inite.fund?

Accepted Answer

Access is invite-only. Submit a request at /invite — we onboard one operator at a time and walk through key generation, capital allocation, and the first trade together.

Question 2

How much does inite.fund cost?

Accepted Answer

Invite-only. There is no public self-serve pricing — the operator tier is shown on the Access page; team and admin tiers are arranged on request.

Question 3

Who is inite.fund for?

Accepted Answer

Operators running their own capital who want a control plane for long-horizon allocation and intraday execution. Not retail self-serve, not full institutional — middle ground. Someone comfortable reading code, generating venue API keys, and approving trades.

Question 4

Do you custody my funds?

Accepted Answer

No. Every strategy reads venue API keys from the operator's encrypted vault — plaintext keys never leave the box. We never custody funds; you remain the sole owner of the venue accounts and the keys.

Question 5

Can multiple users run strategies under one organisation?

Accepted Answer

Yes. The Admin tier supports per-strategy ownership routing across multiple users, three RBAC tiers (viewer / operator / admin), and full audit trail of every operator action. The trading engine reads venue keys from each strategy's owner, so users don't share credentials.

Question 6

What strategies does inite.fund run?

Accepted Answer

Two engines. A long-sleeve macro-regime portfolio across BTC, SPY, GLD, and short-duration bonds with weekly rebalance and a drawdown throttle. An intraday levels-and-zones engine running B-only confluence in maker mode. Suggested split is 80% long sleeves, 20% intraday.

Question 7

How does the Claude / MCP integration work?

Accepted Answer

We expose 14 MCP tools across three RBAC tiers, plus six markdown skills installable with one curl command into ~/.claude/skills/. The dashboard's RBAC and audit log are the same surface — every chat-driven action lands in audit_log with operator id, action, and idempotency key.

By invitation.
One operator at a time.

Run the desk.

Run a team.

By invitation. One operator at a time.

Run the desk.

Run a team.

By invitation.
One operator at a time.