Run your Reg D fund on the operating system — from raise to K-1s
Investor onboarding, cap table, distributions, waterfalls, and multi-state K-1s on one platform, with the official register maintained by an SEC-registered transfer agent. The manager promises. AKRU operationalizes. The platform proves.
Reg D 506(b) / 506(c)SEC-registered transfer agentKYC / AML built inK-1s that tie to the pennyRuns alongside your stack
The problem
Your fund runs on a stack that doesn't talk to itself
Most sponsors run a Reg D fund on spreadsheets and three vendors: one tool for investor reporting, an accountant for K-1s, and a spreadsheet for the waterfall. Every quarter you reconcile between them by hand, and every K-1 season you hope the allocations tie. They don't always tie — and when they don't, it's your team that finds out in March, one LP call at a time.
What AKRU operationalizes
The whole fund lifecycle, on one event fabric
506(b) / 506(c) workflows
Offering workflows for both exemption paths, with the subscription, verification, and closing steps sequenced in the platform rather than in an inbox.
Accreditation & KYC rails
Identity verification, accreditation, and AML screening built into onboarding — compliance is handled before an investor funds, not audited after.
Cap table & registrar of record
One cap table as the source of truth for every downstream figure, maintained as the official register by a registered transfer agent.
Distributions & waterfalls
The waterfall computed from the same record the distributions pay from — preferred returns, splits, and catch-ups with nothing to reconcile.
LP portal
Statements, capital activity, documents, and K-1s in one identity-bound portal your investors log into — no wallets, no crypto experience required.
K-1 engine
87% of K-1 content auto-derived from the cap table, multi-state support, and a QA gate that blocks any allocation off by more than $0.01 from Schedule K totals.
Transfer agent of record
AKRU is an SEC-registered transfer agent — your fund's recordkeeping is operated by a regulated entity, not a software subscription. What that means →
Moving an existing fund
Migration is a registrar change — not a re-papering
Bringing an existing fund onto AKRU is a recordkeeping migration: the fund appoints AKRU as its transfer agent and registrar of record, and your investor records, positions, and distribution history are imported and reconciled onto the platform. That's the whole event — zero disruption to the fund's legal structure, offering documents, or LP relationships. Your fund docs don't change. Your LPs don't re-subscribe. The security an investor holds the day after migration is the same security they held the day before; what changes is where the official register lives and how much of your quarter it takes to maintain. Sponsors have moved hundreds of LP positions this way without missing a reporting cycle.
Proof
Numbers from live deployments
549
LP positions migrated from a prior platform in one registrar change
$0.01
per-distribution processing cost on platform rails
87%
reduction in fund administration time reported across deployments
Questions sponsors ask
Frequently asked questions
Do we have to change our fund documents to move to AKRU?
No. Moving an existing fund onto AKRU is a registrar change — a recordkeeping migration. Your operating agreement, PPM, and subscription documents stay as they are; what changes is the entity maintaining the official register and the system it runs on.
What happens to our current cap table?
It is imported and reconciled during onboarding — investor records, positions, and distribution history — and becomes the register of record on the platform. From that point, every distribution and tax figure derives from that single record, so there is nothing to reconcile between systems.
How long does onboarding take?
Honestly: it depends on the state of your records. Onboarding is typically measured in weeks, not months, and we scope the timeline at intake — after we've seen your cap table, distribution history, and fund documents — so the date you get is one we can stand behind.
Do our LPs need wallets or crypto experience?
No. LPs log into a portal with identity-bound access — no crypto experience, no self-managed keys, nothing to install. The permissioned infrastructure runs underneath; your investors see statements, documents, distributions, and K-1s.
Put your next fund — or your current one — on the operating system
A 15-minute call mapped to your fund structure, not a demo script.
