Bitcoin yield, specialty lending, and data-center land work remain separate by default.
Private capital operating model
Sky Key Group
Ring-fenced capital programs for families that want structure before access.
Sky Key Group presents each mandate on its own terms. The public layer explains scope, guardrails, and admission. Private materials move only after fit is clear.
Truth-lock boundary
The public site should prove structure, discipline, and boundaries before asking for trust.
The site speaks to concentrated allocators, not broad retail intake.
The relationship is intentionally narrow and capacity-aware.
Each sleeve is admitted separately.
Private materials open after qualification, not before.
Public copy should describe structure, not promise outcomes.
Structural proof
The public layer should prove boundaries before it asks for trust.
The job of the homepage is not to imitate an institutional dashboard. It is to make the operating model legible, restrained, and auditable.
One relationship, separate rooms.
The allocator relationship may sit above the platform, but mandate evaluation, materials, and reporting remain separate.
The site should prove boundaries first.
A credible public surface explains what is in scope, what is qualified, and what remains private.
Restraint is part of the trust layer.
No exaggerated product claims. No simulated institutional proof without evidence. No blended risk story.
Operating model
One relationship can sit above the platform. Evaluation, materials, and reporting remain separate.
Institutional tone comes from disciplined pathing and explicit scope. The site should show exactly what is public, what is qualified, and what remains private.
Public layer
What the public site is allowed to do
State the mandate structure, the qualification standard, and the boundaries around access.
Qualified layer
What opens after fit is established
Sleeve-specific materials, reporting expectations, and document access can open only after the correct path is identified.
Private layer
What stays out of public view
Detailed diligence, family-specific room access, and any private operating detail stay behind qualification.
Mandate breakdown
Each vehicle needs its own case for capital.
Separate theses, separate guardrails, and separate admission logic do more trust work than a blended platform pitch.
Vehicle I
BTC on BTC Yield
Bitcoin income for families who want fluency without becoming a trading desk.
Collateralized institutional lending and basis-style trades designed to compound BTC exposure with explicit risk boundaries.
140% minimum initial collateral ratio
125% maintenance threshold and 118% forced liquidation trigger
10-15% max exposure to any single counterparty
Vehicle II
Specialty Real-Estate Lending
Short-duration, overcollateralized capital in micro-markets where local judgment matters more than generic credit models.
Selective lending for residential and commercial situations, centered on high-conviction Miami micro-markets and anchored by hard collateral discipline.
Primary focus on Miami with specialty familiarity in 33149
Hard max 70% LTV
Maximum term of 24 months
Vehicle III
Data-Center Rezoning
Land value creation in power-adjacent corridors where entitlement work can rerate basis materially.
Acquire industrial land with data-center potential, run a short but rigorous feasibility and entitlement process, then move only when the path is real.
Non-flood, non-agricultural industrial land only
Power and utility feasibility before commitment
Land-use counsel scoring during diligence
Proof boundary
Separate what is public, what is qualified, and what is not published.
This prevents the site from claiming institutional proof, live product depth, or compliance posture that has not yet been verified.
Publicly stated
Mandate structure, admission standard, high-level guardrails, and qualification process.
Available after qualification
Sleeve-specific materials, access paths, and further diligence artifacts tied to fit.
Not published
Any claim that would imply verified compliance, institutional backing, or live product capability without proof.
Admission path
Private materials move only after fit.
The site should show the qualification logic in full. It should not pretend the public layer is the product itself.
Establish mandate fit
The first step is a controlled read on sleeve fit, structure preference, and expected first allocation size.
Open the correct room
The next step is not a generic portal. The family is routed to the sleeve path that matches the mandate under review.
Continue privately
Private memos, files, and reporting expectations move into a narrower room once the fit is clear enough to proceed.
Qualification
Choose the right sleeve before anything private opens.
The next step is a direct qualification conversation about mandate fit, structure, and whether the relationship belongs inside the platform at all.