--- title: Prypco Clone Features description: "Explore Prypco Clone features for fractional property investment, secondary trading, rental distributions and XRPL tokenization, deployable in 6 working days." url: https://miracuves.com/prypco-clone/features date_modified: 2026-10-19 author: miracuves language: en_US --- Prypco Clone · Features # Prypco Clone Features: Eleven Revenue Lines Sharing One Wallet, One Identity Check and One Ledger Most fractional property platforms are one product with a long settings page. This one is eleven commercial product lines that happen to share a chassis: fractional property with an SPV behind each building, a secondary marketplace, scheduled exit windows, rental distributions, vaulted gold, mortgage, golden visa, an agent network, real estate services, wills and a CRM. The reason that matters is commercial rather than technical. Verifying an investor costs the same whether they then buy one product or five, so breadth is how acquisition cost gets amortised rather than repaid once. [Request a Live Demo →](https://miracuves.com/schedule-consultation/)[Demo Logins](/prypco-clone/) **11** product lines, one chassis **108** data models behind them **1** identity check per investor **XRPL** mirrored, sandbox by default One checkEleven doors What One Verified Investor Reaches 01Identity verified once 02One wallet, one ledger account 03Property shares inside an SPV 04Marketplace, exit windows, voting 05Mint, Mortgage, Golden Visa, Will 06Agents and CRM on the same record 11Commercial Product Lines 108PostgreSQL Data Models 299API Route Groups 46+Admin Console Suites By Role ## Feature Set by Role Eleven product lines only hold together if the people running them are not each working in a separate tool. Five operator dashboards plus a super admin, an agent channel and the investor experience all read the same records. 01 ### Investor - One portfolio covering property shares, vaulted gold and every other line held - One wallet and one ledger account, opened at registration in the same transaction as the investor record - Certificates issued on allocation, not promised for later - Distribution statements with gross, tax, fee and net on every line - Secondary listings, offers and counters against holdings that are actually held - Exit window eligibility, and a share-weighted vote when a whole property is proposed for sale - Sixty plus screens of this on iOS and Android, built in Expo and React Native rather than wrapped in a WebView 02 ### Agent, on mx One - A pipeline of introduced investors tied to the same identity records the compliance team reviews - Collect, so an agent can take money in on behalf of an investor rather than sending them away to do it - Commission advances, which is the feature that decides whether good agents stay on the channel - Point tiers and referral economics, both configurable by the operator rather than fixed in code 03 ### Operations Manager - Property lifecycle from draft through to live, with the SPV that holds it created as a record rather than as a note - Share classes per property, and the token classes that mirror them - The tokenisation queue, where a chain operation waits for a second signature before it is submitted 04 ### Finance Manager - A double-entry ledger built from LedgerAccount, LedgerTransaction and LedgerEntry rather than a balance column - Distribution batches with gross, tax, fee and net per line, approved before execution - Ten fee types to configure: management, performance, platform, acquisition, disposition, servicing, early exit, FX spread, marketplace listing and marketplace transaction 05 ### Compliance Officer - KYC cases raised against the verification provider you connect, with Sumsub implemented as the reference adapter - Investor classes and the eligibility rules that decide what each class may buy - Audit search across resource, action, actor and time range - Dual control on the chain signing queue, so no single operator can move a token operation alone 06 ### Investment Director - The acquisition pipeline, from a candidate property to a live offering - Exit window design: opens and closes dates, valuation date, pricing method, exit fee percentage and minimum holding days, all per window - Property sale proposals put to a share-weighted investor vote, with settlement paying the register 07 ### Super Admin - Forty six plus console suites, which is the second product inside this platform and the reason the other six roles have somewhere to work - Provider configuration across payments, identity, storage, email, push, metals pricing, AI, maps and FX, each with health surfacing - The VaultSecret layer, where credentials live instead of in environment files pasted between people Each deployment is an isolated sibling rather than a tenant in a shared system: its own database, its own provider accounts, its own branding and its own jurisdiction profile. That is a deliberate trade. It costs more to run than multi-tenancy and it is the only arrangement under which the sentence "we hold the register" is true when someone asks you to prove it. Compare ## Prypco vs Miracuves Clone vs Building From Scratch Three routes to the same category, set against what each one leaves you holding afterwards. | What you are deciding | Prypco, used as a customer | Prypco Clone from Miracuves | Building from scratch | | --- | --- | --- | --- | | Who holds the source code | Not something a customer receives | You do, on delivery: the Next.js 15 web application, the Expo mobile client and the Prisma schema | You do, once it exists | | Who holds the ownership register | The operator you signed up with | You do, append only, on your own PostgreSQL instance | You do, after you have designed one | | Product lines live on day one | Whatever that operator has chosen to offer | Eleven, already sharing one wallet, one identity check and one ledger | One, and then a roadmap | | Tokenisation | Not a decision available to a customer | XRPL issued-currency tokens with authorized trust lines and NFToken certificate offers, shipped against a deterministic sandbox | A research project before it is a feature | | The agent channel | Not a surface a customer sees | mx One: Collect, commission advances, point tiers and referrals, posting into the same ledger | A second product to specify before you can start it | | Time to a branded deployment | Not applicable, because it is their brand | Six days, with app store approval excluded from that count | Discovery before anyone can give you an estimate | | The regulatory licence | Theirs, and it does not transfer | Yours. The platform is the system of record a licensed operator needs; it is not a regulated entity | Yours, and still the long pole | The first column describes what being a customer of an existing platform means for an operator who wants to run their own. It is a statement about your position, not a claim about how anyone else builds their software, and we make no such claim. The cost side of the same three-way choice, including what the sixth day does and does not cover, is on the [Development Cost](/prypco-clone/development-cost/) page. End to End ## How It Works End to End One investor, one verification, and the seven stages the platform actually runs them through. The order is the platform's, not a narrative convenience. Stage 1 ### Verify the person once Registration creates the user, the investor record, the wallet and the ledger account together. A KYC case is raised against whichever verification provider you connect during delivery, and the investor class that comes out of it governs what this person may buy across every one of the eleven lines rather than only the first one they came for. The expensive part of acquiring an investor happens here, and it happens once. Stage 2 ### Stand up the property and the vehicle that holds it A property is drafted, underwritten and attached to the SPV that will hold it, with share classes defined against that vehicle. Token classes mirror the share classes. Nothing is visible to an investor until the operator makes it so, and the documents belonging to the property, the SPV and the share class attach separately because in practice different people produce them at different times. Stage 3 ### Take the money and record the ownership in one transaction A signed payment webhook drives allocation, then the ownership append, then certificate issue, inside a single database transaction. There is no intermediate state in which money has arrived and ownership has not recorded, which is the failure that turns into a reconciliation project at exactly the moment you can least afford one. The webhook secret ships as a sandbox placeholder and must be rotated before this path carries real money. Stage 4 ### Mirror the shares on chain, if you want them mirrored XRPL issued-currency tokens carry authorized trust lines, so who may hold a token is gated at the protocol level rather than only in your application. Certificates can be offered as NFTokens. Every chain operation queues for a second signature, and a ChainEvent indexer reads back what landed. The rule the build holds to: the chain mirrors, the register decides. If the two disagree, the append-only register is the legal source of truth and the chain is the copy. Stage 5 ### Pay the rent out Rent and expenses aggregate into a distribution batch with gross, tax, fee and net on every line. Approval sits before execution rather than after it, and execution posts balanced double-entry pairs with statements attached. Corrections are posted as compensating entries, never as edits, so a distribution run from two years ago still reads the way it read on the day it ran. Stage 6 ### Open the three doors out Liquidity is the hardest problem in this category and the platform does not pretend one mechanism solves it. There are three. A secondary marketplace where an investor lists, receives offers, counters and settles against the register. Scheduled exit windows with opens and closes dates, a valuation date, a pricing method, an exit fee percentage and a minimum holding period, all per window. And a whole-property sale the operator proposes and investors decide by share-weighted vote. All three move ownership through the same append-only history. Stage 7 ### Sell them the second thing The investor from stage one is now verified, funded and inside a wallet. mx Mint sells them vaulted gold priced from a metals provider. mx Mortgage, mx Golden Visa, mx Real Estate services and mx Will each run against the same identity record and document store, and the CRM tracks all of it as one relationship. Nothing in stages two to six has to be repeated to open any of those doors, and that is the difference between a platform with eleven products and eleven platforms. All seven stages write into the same 108-model domain across 299 API route groups, which is why an investor statement, a finance report and an audit search in the console read the same underlying facts rather than three systems that have to be made to agree afterwards. The Economics of Breadth ## Every Feature Earns Its Place Eleven product lines is only an advantage if each one either earns directly or makes another one earn more. Here is the whole list with that test applied to it. | Product line | What it adds for someone already inside your funnel | Where the operator's money comes from | | --- | --- | --- | | Fractional property investment | Shares in a specific building, held through an SPV, with a certificate issued at allocation | Management and performance fees, plus the acquisition and disposition legs of the transaction schedule | | Secondary marketplace | A way out that does not require the operator to find a buyer: list, receive offers, counter, settle against the register | Marketplace listing and marketplace transaction fees | | Exit windows and liquidity governance | A scheduled door with a valuation date, a pricing method and a minimum holding period stated in advance | The per-window exit fee percentage, and early exit fees where the window allows an early release | | Rental distributions | Income arriving in the same wallet the shares were bought from, with gross, tax, fee and net all shown | The servicing fee on the distribution run | | mx Mint | Vaulted gold bought in the same wallet, priced from a metals provider, for the investor who wants a second asset without a second signup | The gold spread | | mx Mortgage | A financing conversation that stays inside the platform rather than ending it | Operator-set fees from the ten-type schedule; the build ships the schedule, you set the rates | | mx Golden Visa | A residency application tracked against an identity record that is already verified and already holds property | Operator-set fees from the same schedule | | mx One | An agent who brings investors in, takes money on their behalf through Collect, and stays because commission advances exist | Agent channel economics: commissions, advances, point tiers and referrals | | mx Real Estate services | The transactional work around a property that the investor would otherwise take to someone else | Operator-set fees from the same schedule | | mx Will | Succession recorded against the same holdings, which is the question every long-horizon investor eventually asks | Operator-set fees from the same schedule | | CRM and investor relations | One relationship record rather than eleven, which is what makes any of the cross-sell above possible to execute | No direct fee. It is the line that raises the yield on the other ten, alongside the growth levers: promo codes, sponsored listings and partner ad slots with impression and click counters | Nine revenue rails are configurable per deployment and ten fee types are named in the schedule. None of them is switched on by default at a rate we have chosen for you, and nothing on this page is a promise about returns, yields, occupancy or rent. How an operator actually sequences these rails, and which ones are worth opening in the first year, is the subject of the [Business Model](/prypco-clone/business-model/) page. Read This Before Anything Else ## What Is Not Included in the Base Package A page listing eleven product lines invites assumptions about licensing, custody and production readiness. These are the ones to discard now, before they cost you a quarter. 01 ### No sanctions or PEP screening Not included and not implied. Identity verification is wired to a provider adapter; screening a verified person against sanctions and politically exposed person lists is a separate piece of work, as is defining how a match is handled and who reviews the queue. Most regulators will expect all of it in place before you operate. 02 ### No regulatory licence or approval, anywhere Buying this software is not a step in a licence application and does not grant permission to raise capital from the public in any jurisdiction. The platform is the system of record a regulated operator needs. It is not a regulated entity, it does not hold client money, and whether you may operate is a question for your counsel and your regulator. 03 ### Live provider credentials are yours to bring Four payment providers are implemented in the build: Stripe, Razorpay, Plaid and NOWPayments, with Sumsub as the reference identity adapter. They run on sandbox credentials, as a demo should. PAYMENT_WEBHOOK_SECRET ships as a sandbox placeholder and must be rotated before the settlement path in stage three carries real money. Connecting your own accounts is delivery work under your commercial relationships, not a property of the shipped build. 04 ### The chain ships in a sandbox XRPL tokenisation is real, and it runs against a deterministic sandbox by default. The admin screen prints the word sandbox so nobody is in any doubt. Pointing it at testnet or mainnet means an RPC endpoint and an issuer account held in secrets management, and that is your configuration decision. The local vault is not production custody; the build's own mainnet checklist says so. 05 ### Single node until two stores move to Redis The rate limiter and the WebAuthn credential store are in-process today, which means this deployment runs on a single node until both are moved behind Redis. It is a known and scoped item rather than a surprise, and it is the honest answer to a question that institutional diligence will ask. 06 ### Six days is a deployment, not a licence to open A branded deployment takes six days, with app store approval excluded from that count. That is not the same thing as being ready to take public money. Screening, live rails, counsel, a licence and the hardening items above all sit between the two, and anyone telling you otherwise is selling you the first week and leaving you the rest. The independent security review returned one Critical, seven High, five Medium and two Low. The Critical is a data-classification label rather than an exploitable finding, and we will not present it as one in either direction. Against that list, what ships is real and demonstrable on day one: the eleven product lines, the append-only register, the double-entry ledger, the single-transaction allocation path, the dual-control chain queue, the forty six plus console suites, and sixty plus mobile screens in eight interface languages including Arabic with full right-to-left layout. Stack ## The Technology Behind the Features Eleven product lines on one chassis is an architecture decision long before it is a settings page. Here is where each part of it lives. **Web and operator console**Next.js 15 on the App Router, serving the investor experience and forty six plus operator suites across one hundred and sixty plus routed pages from a single codebase, with one shared design system package so a new product line does not arrive looking like a bolt-on. Eight interface languages ship, including Arabic with full right-to-left layout rather than translated strings inside a left-to-right shell. **Domain model**PostgreSQL through Prisma migrations with 108 models: property, SPV, share class, token class, ownership, ledger, distribution, compliance, agent channel, CRM and the seven mx product lines as one connected graph rather than eleven schemas that have to be joined by a nightly job. **The ledger and the register**A double-entry engine built on LedgerAccount, LedgerTransaction and LedgerEntry, with balances derived from balanced entries and corrections posted as compensating entries instead of edits. Beside it, the append-only ownership register, which is the legal source of truth and the thing every other subsystem defers to. **API layer**299 route groups spanning the web application, the mobile client and the operator console. The allocation path is the one worth reading first: a signed payment webhook drives allocation, ownership append and certificate issue inside one database transaction, which is why there is no window in which money has arrived and ownership has not recorded. **Mobile**Expo and React Native, iOS and Android, sixty plus native screens built from the same source you receive. It is a native client, not a WebView wrapper around the website, and the EAS build configuration for both stores is included. Store signing, listing and release remain their own piece of work under your developer accounts. **Chain layer**XRPL issued-currency tokens with authorized trust lines, so compliance gating exists at the protocol level and not only in your application logic, plus NFToken certificate offers, a dual-control TokenOperation signing queue and a ChainEvent indexer reading back what landed. It runs against a deterministic sandbox by default, and the admin screen says so. **Provider seams and security primitives**Adapters for payments, identity verification, S3-compatible storage, SMTP email, push and notifications, metals pricing, AI, maps and FX, each connecting to accounts you hold and each surfacing its health in the console. Underneath: sessions, passkeys, TOTP, device registration, rate limiting, the VaultSecret credential layer, magic-byte upload validation and per-investor document scoping. None of it is bolted on per product line. Every layer here is mainstream and widely hired for, a Docker image is included, and the schema is portable to any PostgreSQL instance. That last point matters more than it reads: you will own this system for as long as investors hold shares on it. Development Cost ### What eleven product lines cost to buy rather than build The fixed price, what the six days cover, what the hardening pass adds, and which of the not-included items above carry a cost of their own - on the Development Cost page. [See the pricing →](/prypco-clone/development-cost/) FAQ ## Frequently Asked Questions Are all eleven product lines actually in the base build? Yes, and they share one wallet, one identity check and one ledger rather than sitting beside each other. The eleven are fractional property investment, the secondary marketplace, exit windows and liquidity governance, rental distributions, mx Mint, mx Mortgage, mx Golden Visa, mx One, mx Real Estate services, mx Will, and the CRM. They are backed by 108 data models and 299 API route groups, and that volume of domain is what eleven lines sharing one ledger costs. What is configurable is which of them you open and at what fees, not whether they were built. Is the XRPL tokenisation live or is it a demo? It is real code running against a deterministic sandbox, and the admin screen prints the word sandbox so nobody can be confused about which one they are looking at. Issued-currency tokens with authorized trust lines, NFToken certificate offers, a dual-control signing queue and a ChainEvent indexer are all in the build. Moving to testnet or mainnet is your configuration: an RPC endpoint and an issuer account held in secrets management. The rule that governs the whole design is that the chain mirrors and the register decides, so the append-only ownership register remains the legal source of truth whatever the chain is pointed at. How does the platform stop money arriving without ownership being recorded? By refusing to let those be two separate events. A signed payment webhook drives allocation, the ownership append and certificate issue inside a single database transaction, so there is no intermediate state where the money is in and the register has not moved. The honest qualification is that the webhook secret ships as a sandbox placeholder and must be rotated before that path carries real money, and connecting your own payment processor with its own signature verification is delivery work rather than something the shipped build can do for you. What does mx One give an agent that a referral link does not? Three things that decide whether good agents stay. Collect, so an agent can take money in on behalf of an investor instead of sending that investor away to pay and hoping they come back. Commission advances, so the agent is paid before the distribution cycle rather than after it. And point tiers plus referral economics that the operator configures rather than inherits. All of it accrues into the same double-entry ledger as every other line, so the agent channel is never a spreadsheet kept beside the books. Do I need a licence to run this? Almost certainly, and the software does not provide one. This platform holds no regulatory licence or approval in any jurisdiction, it is not a regulated entity, and it does not hold or safeguard client money. Raising capital from the public is a regulated activity in most markets, so you will need counsel and either a licence or an exemption. What the platform gives you is the system of record a licensed operator needs: KYC cases, investor classes, the append-only register, audit search, dual-control approvals and a double-entry ledger that an auditor can read. What is not included that I should budget for? Five things, all of them named on this page rather than discovered later. Sanctions and politically exposed person screening is not included. Live provider credentials are yours to bring, and the sandbox webhook secret must be rotated. A regulatory licence is yours. Chain activation beyond the sandbox is your configuration decision. And the rate limiter and WebAuthn credential store are in-process, so the deployment is single-node until both move to Redis. The six-day delivery figure covers a branded deployment with app store approval excluded; it is not a statement that you are ready to take public money on day seven. ## Open one product line, then open the next one Sign in to the investor demo, buy into a property, then open mx Mint from the same wallet without verifying anybody twice. Then sign in to the operator console and read what both movements did to the ledger. [Request a Live Demo](https://miracuves.com/schedule-consultation/)[Full Overview](/prypco-clone/) Explore ## Explore the Prypco Clone Five pages on this product. You are on Features. [Overview ### The product page Back to overview→](/prypco-clone/) You are here ### Features Eleven product lines, by role. [Development Cost$6,999 ### Fixed price See exact pricing→](/prypco-clone/development-cost/) [Development Company ### Who should build it Compare options→](/prypco-clone/development-company/) [Business Model ### How it earns See the playbook→](/prypco-clone/business-model/) ## Eleven product lines, one verified investor. One wallet, one identity check and one append-only register behind every line, with the source code yours, the database yours and the sandbox stated rather than hidden. [Talk to Us →](https://miracuves.com/schedule-consultation/) **Written by the Miracuves Product Team**· Reviewed for accuracy· Last updated **October 17, 2026** Miracuves · Prypco Clone Capabilities, counts and stated limitations cross-verified against the MXPropstake platform documentation, 2026-10-17 Disclaimer Miracuves is an independent software development company. We are not affiliated with, connected to, sponsored by, or endorsed by **Prypco**. Why this name “**Prypco** Clone” is used descriptively. It is how the software industry refers to building a platform with functionality similar to Prypco, and how clients search for it. Who built this The entire design and codebase is built by our own team. The product contains no code, design, graphics, or content originating from the Prypco website or applications. Trademarks **Prypco** and all other third-party names and marks are the property of their respective owners, referenced here solely to describe the category of software offered. [Read our full Legal Notice & Disclaimer →](/disclaimer/)