Three ways to deploy it, four ways to license it
Portfolio 360 is designed to sit inside someone else's business. The integration path and the commercial model are chosen separately, so you are never forced into either.
Deployment models
Hosted white-label
We run the platform, you own the brand. Your theme, your domain, your terminology, your support flows.
- Fastest route to market
- No infrastructure work on your side
- Single sign-on into your existing accounts
Embedded modules
Authenticated portfolio, performance and reporting views mounted inside your own application shell.
- Keep your navigation and layout
- Token-based session hand-off
- Per-module rollout
API-first
Use Portfolio 360 purely as a portfolio accounting and analytics engine behind an interface you build.
- Documented REST API
- Webhooks for valuation and report events
- You own the entire UI
How data flows
Positions and transactions come in, valuation and analytics happen in the engine, and results go out to whichever surface you licensed.
Broker / custodian feeds ─┐
Market data ──────────────┤
CSV & manual holdings ────┼──▶ PORTFOLIO 360 ENGINE
Your core system API ─────┘ · normalisation
· valuation & FX
· performance & risk
· report generation
│
┌─────────────────────────────┼─────────────────────────────┐
▼ ▼ ▼
White-label app Embedded modules REST API
(your brand) (inside your product) (your own UI)
A typical onboarding
Indicative timeline for a hosted white-label deployment. API-only integrations are usually faster; complex custodian estates take longer.
Scoping & data mapping
Confirm asset coverage, data sources, entity model and reporting requirements.
Connect & ingest
Wire up broker/custodian feeds, market data and historical positions; validate valuations.
Brand & configure
Apply your theme, report templates, roles and permissions; configure model portfolios.
UAT & go-live
Parallel-run against your existing numbers, train the team, then launch to clients.
Security & data posture
Licensees are regulated businesses, so the platform is built to survive their due diligence.
Access control
Role-based permissions, least-privilege defaults, SSO support and a full audit trail of every action.
Data handling
Encryption in transit and at rest, per-tenant isolation and configurable data residency for your jurisdiction.
Operational controls
Backups, point-in-time valuation records, retained report copies and documented incident procedures.
Licensing models
Every licence includes the core platform, updates and support. The difference is how it is metered.
Platform licence
Annual licence for brokerages and platforms deploying Portfolio 360 to their whole client base. Priced on platform scale, not seats.
Per-seat licence
For advisory and asset-management firms. Priced per adviser or operations seat, with unlimited client records within your tier.
AUM-tiered licence
Priced against assets under administration on the platform. Suits managers whose seat count is small relative to the book.
Embedded / OEM
For fintechs reselling portfolio functionality inside their own product, including API volume terms and co-branding rights.
Let's scope your integration
Bring your data sources and your client model — we'll tell you which deployment and licence fits.