Operator invites into a role
Pick an organisation already on the network or invite a new one. The proposal carries the fund, the role and the scope of access it grants.
Product
The fund lifecycle, coordinated end to end.
Artery is one system shared by the operator and every service provider on a fund. It carries the fund from first launch step to ongoing governance, and records the whole path as it goes.
01 — Lifecycle
Launch is a workflow, not a folder.
A launch is modelled as a sequence of steps with an owner, a dependency and an outcome. The system knows which step is live, who is holding it, and what has to be true before the next one opens.
What the workflow carries
- Fund identity, structure and jurisdiction captured once, reused everywhere.
- The roles the fund needs filled, and the provider engaged into each one.
- Step-level ownership across organisations, not just inside your own team.
- Blocking conditions made explicit — what is waiting, and on whom.
- Timeline pressure surfaced before it becomes a slipped launch date.
Launch templates are configurable per fund type, so the step list follows your own house process rather than a fixed sequence imposed by the software.
Create fund · step 1 of 5
1 Identity2 Operating model3 Cadence4 Jurisdiction5 Review
NameLux Private Equity IRAIF
VehicleSCSp · EUR · closed-endedLuxembourg
AIFMVertex AIFM SàrlEngaged
AdministratorAtlas Fund ServicesWill propose
DepositaryNot assignedRequired
Illustrative interface — sample data, not a live fund.
02 — Cross-organisation engagement
Engagement is a two-sided handshake, and it is recorded.
Appointing a provider is not an email. In Artery the operator proposes an organisation into a named role on a named fund; the provider accepts, declines, or is substituted — and every one of those outcomes is part of the record.
Provider responds in its own portal
The counterparty reviews the engagement and accepts or declines. Acceptance is what creates access — nothing is opened up unilaterally.
The role is filled, and stays filled
The binding persists across the fund's life. Substituting a provider is an explicit, recorded act with a beginning and an end — not an overwrite.
Engagement request
FundLux Private Equity IRAIF · SCSp
RoleFund administratorProposed
Proposed byLux Management SA12 Mar, 09:14
ScopeNAV production, investor register, reporting pack
Accept engagementDeclinePropose substitute
Illustrative interface — sample data, not a live fund.
03 — Coordination surfaces
Every party has one place that says "your move".
The daily product is a decision queue. Whatever is waiting on you — across every fund and every counterparty — arrives in one list with the context needed to resolve it.
My Work
A single queue of pending decisions: engagements to answer, documents to return, attestations to sign, approvals to give. Each item opens with its fund, role and deadline attached.
Requests
Structured asks between organisations — a document, an attestation, a piece of information — with a defined recipient, a due date and a resolution state.
Documents
Documents are attached to the step and party they belong to, versioned, and reachable from the workflow instead of a parallel drive.
Network
The map of organisations you work with, the roles they hold and the funds they are engaged on — your provider relationships as data rather than memory.
My Work · 6 open items
BlockedDepositary attestation — Phoenix Fund2dCritical
AwaitingAccept administrator engagementtodayYou
RequestReturn signed LPA counterpartdue 14 MarOpen
ReviewBoard resolution — director change1dYou
DoneAIFM engagement accepted11 MarClosed
Illustrative interface — sample data, not a live fund.
Organisation profile
OrgAtlas Fund Services S.A.LuxembourgConnected
Roles heldAdministrator on 4 funds · Registrar on 2
Contactops@atlasfundservices.luverified
ResponsivenessMedian acceptance 1.4 dayslast 90d
Open items2 requests · 0 overdueHealthy
Illustrative interface — sample data, not a live fund.
04 — Audit trail
The trail is a by-product of the work, not a task after it.
Because coordination happens inside the system, the evidence is created at the moment of the act. There is nothing to reconstruct later from mailboxes.
- Every action is sequenced, timestamped and attributed to a named user at a named organisation.
- Engagements, substitutions, declines and approvals are all first-class recorded events.
- Records are appended rather than quietly edited, so history stays intelligible.
- The fund's history can be read as a single chronological trail, per fund or per party.
- Export supports internal review, board reporting and provider oversight files.
History can be exported for a fund or a counterparty as a structured file for internal review, board reporting and provider oversight packs.
Decision record
DecisionAppoint depositary — CACEISApproved
PrincipalS. Weber · Lux Management SA14 Mar, 16:02
EvidenceDepositary agreement v3 · board minute2 files
SHA-256
9f2c4a…b71e08VerifiedIllustrative interface — sample data, not a live fund.
05 — The operator journey
Four moves from board approval to a running fund.
This is the path a conducting officer or fund operations lead walks, in order, from the moment a structure is approved.
Create the fund
Regime, vehicle, target size and intended first close, captured once. The launch workflow is generated with an owner on every step.
Engage the providers
Propose each organisation into its role. They accept by secure link; the appointment step resolves on acceptance rather than by hand.
Run the launch
Work the timeline: request documents against the step that needs them, see what is blocked and on whom, close steps as their outputs land.
Govern and evidence
The launch record becomes the governance record. Overrides carry a mandatory reason; decisions carry a SHA-256 evidence hash.
Create fund · step 1 of 5
1 Identity2 Operating model3 Cadence4 Jurisdiction5 Review
NameLux Private Equity IRAIF
VehicleSCSp · EUR · closed-endedLuxembourg
AIFMVertex AIFM SàrlEngaged
AdministratorAtlas Fund ServicesWill propose
DepositaryNot assignedRequired
Illustrative interface — sample data, not a live fund.
Fund launch · stage 3 of 6
- Formation
- Fund identity & structure
- Appoint management company / AIFM
- Appointments
- Appoint fund administrator
- Appoint depositary
- Evidence
- Constitutional document pack
- Appoint auditor
Illustrative interface — sample data, not a live fund.
06 — The provider journey
Three moves, and no portal onboarding.
Administrators, depositaries, auditors and counsel come in from the other side. The experience is deliberately short.
Receive the engagement
A secure link arrives naming the fund, the role, the operator and the access acceptance would grant. No account to create first.
Accept or decline
Either answer is recorded. On acceptance the binding is created and the fund appears in your own scoped portal.
Deliver against the step
Return documents and attestations against the exact step that asked for them, across every operator client, from one queue.
Engagement request
FundLux Private Equity IRAIF · SCSp
RoleFund administratorProposed
Proposed byLux Management SA12 Mar, 09:14
ScopeNAV production, investor register, reporting pack
Accept engagementDeclinePropose substitute
Illustrative interface — sample data, not a live fund.
Walk a real launch through the system
The fastest way to judge Artery is to watch a launch move through it — proposal, acceptance, request, approval, trail. We will run it with your fund structure in mind.