--- title: UbanBank case study description: MXNEOBANK Case study · November 2024 A digital neobank, deployed as-is delivered in 6 working days. Uba url: https://miracuves.com/portfolio/ubanbank date_modified: 2026-08-18 author: miracuves language: en_US --- MXNEOBANK Case study* · November 2024* # A digital neobank, deployed as-is delivered in 6 working days. UbanBank needed a digital neobank, deployed as-is. The Neobank Solution base already carried the mechanics, so the engagement went where their product was actually different. We built the product; they launched the brand. - **Neobank Solution** · MXNeoBank - **6 working days** our build time on the base - **Source code transferred** to UbanBank’s own account [Read the case study](#summary) [Start a project](https://miracuves.com/schedule-consultation/) *U***UbanBank***Youlife Tecnologia Dell'Informazione S.R.L* *U***UbanBank** SolutionNeobank Solution ProductMXNeoBank DeliveredNovember 2024 StackPHP Build time6 working days Blocks reused17 of 21 Source codeTransferred **3**applications shipped **17**blocks reused unchanged **4**built for this client **9**integrations, each isolated **100%**source code transferred [Summary](#summary)[Scope](#scope)[Brief](#brief)[Discovery](#discovery)[Challenges](#challenges)[Strategy](#strategy)[Market](#market)[What we built](#built)[Architecture](#architecture)[Reused](#reused)[Decisions](#decisions)[Process](#process)[Product](#surfaces)[Security](#security)[Integrations](#integrations)[Stack](#stack)[Timeline](#timeline)[Scale](#scale)[Results](#results)[Handover](#handover)[FAQ](#faq)[Related](#related) Customer app*corridors*Merchant*Fee schedule*Admin*Payment rails*API gateway*Brand & theming*Realtime channelCustomer app*corridors*Merchant*Fee schedule*Admin*Payment rails*API gateway*Brand & theming*Realtime channel ## What already existed, and what did not. The distinction that decides a project like this: the mechanics were proven before the engagement started, so the time went into the part that was theirs. We build the product; the client launches the brand. That is the arrangement, and it only works if the handover is real: UbanBank owns the source code, had a launch date in writing before work started, and can check every figure on this page against a public ledger. We took the neobank clone as it came. Accounts, KYC and card issuing were already built and proven, we needed nothing bespoke on top, and it was deployed and running in four days. That is why we came back the following year for the Revolut build rather than shopping around again. Ho Pei Aik, Founder · Youlife Tecnologia Dell'Informazione S.R.L Reuse on this build Blocks reused17 of 21 Built for UbanBank4 Solution familyNeobank Solution Other builds on it2 ## The line between reused and built. Nothing was built bespoke. The base shipped as it came. Everything else on the list below arrived already built and proven on other engagements running the same base. **3**Applications and consoles shipped, each with its own permissions and release path*Delivered* **17**Platform modules reused unchanged from the Neobank Solution base*Delivered* **4**Decisions built for UbanBank: licence &, corridors, fee schedule*Delivered* **3**Environments: development, staging and production*Delivered* **100%**Source code transferred to UbanBank’s own account*Contractual* ## What UbanBank actually needed. A digital neobank, deployed as-is is not one feature. It is 21 distinct pieces that all have to work together before a single customer can be served, and most of them already existed and had been proven elsewhere. That distinction decides the shape of a project like this. A business does not need a dispatch engine or a settlement ledger to be invented again; it needs one that already works, then it needs the handful of decisions that make the product theirs rather than anyone else’s. The four below are the load-bearing pieces UbanBank would otherwise have spent months building before proving anything to a customer. Every platform of this kind has the same shape underneath: a set of load-bearing parts that must be correct before a single customer can be served, and a much smaller set of decisions that make it one business rather than another. Building the first set from zero would have consumed the window before the second was even discussed. That is the decision this engagement turned on, and it was taken before any code was written. **Customer app**accounts, cards, payments **Merchant**collect, settle, refund **Admin**KYC review, limits, **API gateway**auth, rate limits, ## What we settled before building. Which of the 21 pieces were already solved, and which were genuinely UbanBank’s to decide. Getting that line in the right place before any code is written is what keeps a Neobank Solution engagement short, and it is the conversation we would rather have honestly than optimistically. Where a scope genuinely does not fit a proven base, we say so during scoping and quote it as a custom build instead, even when that costs us the larger and more comfortable project. *01* #### Read the requirement back to first principles What must exist at launch, separated from what a business can add once it has customers. Those are different lists and conflating them is what makes projects run long. *02* #### Base versus build, capability by capability Each of the 21 capabilities assessed against the existing base as covered, partial or absent. Partial is treated as absent, because a half-fitting module costs more than a new one. *03* #### Mark what only UbanBank could decide 4 decisions were commercial or jurisdictional rather than technical. Those were theirs, and the engagement is where they got implemented. *04* #### Agree the line before writing anything 17 pieces reused unchanged, 4 built. Fixing that line up front is what turns a platform of this size into a six-working-day build. ## The parts that are genuinely hard. Not marketing difficulty, actual difficulty. These are the problems any serious Neobank Solution has to solve properly, and the reason building one from a blank page is a multi-quarter commitment rather than a sprint. Each was solved once, on the base, and has been under load on other builds since. UbanBank inherited the solutions rather than the problems. 01 ### Correctness before features Balances, postings and holds have to be right before anything else can ship. Everything else is built on them. **Already solved in the base:** Customer app 02 ### KYC gates the account Identity, screening and limits decide who may hold money, and regulators audit the trail. **Already solved in the base:** Merchant 03 ### Reconciliation never stops The ledger must agree with the card network and the payment rails continuously, not monthly. **Already solved in the base:** Admin ## What we did not have to build for UbanBank. Every platform is made of the same mechanics underneath. This is the account of which of them UbanBank paid attention to, and which were already solved. Built from nothing, UbanBank would have meant paying for the mechanics again: the accounts, the sessions, the payments, the admin, the permissions. That work is real, it is slow, and none of it is what makes this product different from the next one. Starting from the Neobank Solution base moved that cost out of the project entirely, and the platform itself was deployed in 6 working days. What that bought is attention. The engagement went into the 4 parts that were actually different, instead of being spread thin across 21 of them. **Shipped ready-made***17 of 21* *01***Customer app**accounts, cards, payments *02***Merchant**collect, settle, refund *03***Admin**KYC review, limits, *04***API gateway**auth, rate limits, *05***Realtime channel**payment status, *06***Event bus**async fan-out, retries *07***Accounts ledger**append-only double-entry *08***Payments**transfers, standing *09***Card issuing**virtual and physical *10***settlement**collect, settle, refund *11***KYC & AML**identity, screening, *12***chargebacks**evidence, holds, outcome *13***Statements**exports, reporting *14***Identity & access**accounts, roles, devices *15***store**ledger, accounts, *16***realtime**balances, sessions, *17***Object storage**identity documents, **Made for UbanBank***4 of 21* *01***corridors**where you may operate *02***Fee schedule**your pricing *03***Payment rails**your local providers *04***Brand & theming**app and web Build all 21 from nothing, mechanics included 17 already solved, so the effort went to the 4 that were not The account Shipped ready-made17 Made for this client4 Parts in total21 Build window6 working days The ready-made side is not a shortcut taken on quality. It is work that was already finished, and finished work does not get charged for twice. ## What this market demanded. Italy and EU, banking The first engagement for this client, taken as a straight deployment. EU banking brings PSD2 authentication, SEPA rails and KYC obligations that the base already carried, which is why nothing bespoke was required on top. None of that is optional, and none of it is something a platform can guess on a client’s behalf. It is precisely why the 4 decisions listed further down sat with UbanBank rather than with us: they are commercial and jurisdictional questions, and the base exists so that answering them is the whole job rather than the last ten per cent of it. ## Everything that shipped with it. The full working set UbanBank took delivery of. Each piece was already built and proven on other engagements before this one started, which is the only honest reason a platform of this size stands up in six working days rather than months. None of it is a demo or a scaffold. These are the same components running under other businesses in other markets, which means the failure modes are already known and already handled rather than waiting to be discovered by UbanBank’s first real customers. ### Reused from the Neobank Solution base **Customer app**accounts, cards, payments **Merchant**collect, settle, refund **Admin**KYC review, limits, **API gateway**auth, rate limits, **Realtime channel**payment status, **Event bus**async fan-out, retries **Accounts ledger**append-only double-entry **Payments**transfers, standing **Card issuing**virtual and physical **settlement**collect, settle, refund **KYC & AML**identity, screening, **chargebacks**evidence, holds, outcome **Statements**exports, reporting **Identity & access**accounts, roles, devices **store**ledger, accounts, **realtime**balances, sessions, **Object storage**identity documents, ### Built for UbanBank **corridors**where you may operate **Fee schedule**your pricing **Payment rails**your local providers **Brand & theming**app and web ## The base this was built on. The same architecture carries every Neobank Solution on this page. The filled blocks are the parts built for UbanBank. **Neobank Solution architecture** MXNeoBank / filled = built for this client Neobank Solution: the architecture, and one payment traced through it 3 client surfaces reach an edge of gateway, realtime channel and event bus. The base holds 8 services, of which Accounts ledger is the source of truth, and 4 blocks are built for each client. Partner services sit behind a boundary and are chosen by the client. Underneath, one payment is traced across 5 steps. 17 of 21 blocks are reused unchanged. .fdiag{--dg-ink:#1c1618; --dg-sub:#6e6264; --dg-rule:#e3d2d5; --dg-rail:#faf5f6; --dg-card:#ffffff; --dg-accent:#a70d2a; --dg-track:#efe9ea; --dg-made:#a70d2a; --dg-made-ink:#ffffff; --dg-zone:rgba(28,22,24,.028); --dg-zone-core:rgba(167,13,42,.05); --dg-zone-line:#e3d2d5; --dg-zone-core-line:#f0c9d1} .lbl{font-size:13px;font-weight:700;fill:var(--dg-ink);letter-spacing:-.014em} .sub{font-size:10.5px;fill:var(--dg-sub)} .note{font-size:10px;fill:var(--dg-sub);font-style:italic} .mono{font-family:'JetBrains Mono',ui-monospace,monospace;font-size:10px; letter-spacing:.14em;text-transform:uppercase;font-weight:500;fill:var(--dg-accent)} .zn{font-family:'JetBrains Mono',ui-monospace,monospace;font-size:10px;font-weight:500; letter-spacing:.13em;text-transform:uppercase;fill:var(--dg-sub)} .zn.zh{fill:var(--dg-accent)} .tag{font-family:'JetBrains Mono',ui-monospace,monospace;font-size:7.5px;font-weight:500; letter-spacing:.1em;fill:var(--dg-accent)} .h2{font-size:30px;font-weight:800;fill:var(--dg-ink);letter-spacing:-.034em} .deck{font-size:13px;fill:var(--dg-sub)} .zone{fill:var(--dg-zone);stroke:var(--dg-zone-line)} .zone-core{fill:var(--dg-zone-core);stroke:var(--dg-zone-core-line)} .card{fill:var(--dg-card);stroke:var(--dg-rule)} .auth{fill:var(--dg-card);stroke:var(--dg-accent);stroke-width:2} .made{fill:var(--dg-made);stroke:none} .made-l{fill:var(--dg-made-ink);font-size:13px;font-weight:700;letter-spacing:-.014em} .made-s{fill:var(--dg-made-ink);font-size:10.5px;opacity:.95} .step{fill:var(--dg-card);stroke:var(--dg-rule)} .dot{fill:var(--dg-accent)} .dotn{fill:#fff;font-family:'JetBrains Mono',ui-monospace,monospace;font-size:11px;font-weight:500} .flow{stroke:var(--dg-rule);stroke-width:1.5;fill:none;marker-end:url(#mxneobank-ar)} .hot{stroke:var(--dg-accent);stroke-width:2;fill:none;marker-end:url(#mxneobank-ah);opacity:.55} .cnt{font-family:'JetBrains Mono',ui-monospace,monospace;font-size:10px; letter-spacing:.1em;fill:var(--dg-sub)} Neobank Solution MXNeoBank Three documented builds run on this base. Only the filled blocks are built for you. Ships ready-made Built for this client Surfaces Edge The base - already built Partner boundary Data Customer app accounts, cards, payments Merchant collect, settle, refund Admin KYC review, limits, disputes API gateway auth, rate limits, idempotency Realtime channel payment status, notifications Event bus async fan-out, retries Accounts ledger append-only double-entry postings SOURCE OF TRUTH Payments transfers, standing orders Card issuing virtual and physical Merchant settlement collect, settle, refund KYC & AML identity, screening, limits Disputes & chargebacks evidence, holds, outcome Statements exports, reporting Identity & access accounts, roles, devices Built for this client Licence & corridors where you may operate Fee schedule your pricing Payment rails your local providers Brand & theming app and web chosen by the client Banking rails their bank partner Card issuer their BIN sponsor KYC & screening their provider Push & email their sender Transactional store ledger, accounts, identities Cache & realtime balances, sessions, queues Object storage identity documents, statements one payment, end to end every step below runs on blocks that already existed 1 Initiate payee, amount, reference 2 Authorize limits, balance, screening 3 Post double-entry, both accounts 4 Clear rail instructed, status tracked 5 Reconcile rail confirms, statement updated PHP LARAVEL · CODEIGNITER · MYSQL 17 of 21 blocks reused unchanged 4 built for you This is the Neobank Solution base, drawn as it was actually assembled for UbanBank. The plain blocks are the ready-made platform and shipped as they are. The filled blocks are the ones we built for this client. 17 of 21 blocks were reused, 4 were built. ## Why none of this had to be written again. Each of these was already running on other builds of the same base before UbanBank started. That is the whole reason the platform was standing in days rather than months. **Customer app**accounts, cards, payments **Merchant**collect, settle, refund **Admin**KYC review, limits, **API gateway**auth, rate limits, **Realtime channel**payment status, **Event bus**async fan-out, retries **Accounts ledger**append-only double-entry **Payments**transfers, standing **Card issuing**virtual and physical **settlement**collect, settle, refund **KYC & AML**identity, screening, **chargebacks**evidence, holds, outcome **Statements**exports, reporting **Identity & access**accounts, roles, devices **store**ledger, accounts, **realtime**balances, sessions, **Object storage**identity documents, ## The decisions that were actually theirs. A ready-made base does not remove these; it removes everything underneath them. Each one below is a choice UbanBank had to make, and the engagement is where those choices got implemented. **01** ### Licence & Configured for UbanBank during the engagement. **Why it sat with them**Commercial rather than technical. The base already handles the mechanics underneath, so the engagement is where their own answer gets implemented. **02** ### corridors Configured for UbanBank during the engagement. **Why it sat with them**Commercial rather than technical. The base already handles the mechanics underneath, so the engagement is where their own answer gets implemented. **03** ### Fee schedule Maker, taker and withdrawal pricing. **Why it sat with them**Take rate and pricing are the business model itself. We implement the numbers they set; we do not choose them. **04** ### Payment rails The local providers money actually moves through. **Why it sat with them**Which processor sits behind the wallet follows from their jurisdiction, banking relationship and settlement terms. None of that is a technical choice. **05** ### Brand & theming The identity carried across every surface, so it reads as the client’s product rather than a template. **Why it sat with them**The base has to disappear behind their identity, so this is applied across every surface rather than skinned on one. ## What the six days actually cover. Our build time on a ready-made base, and nothing else. The parts that sit with the client are named plainly. Phase 01Phase 02Phase 03Phase 04 01 ### White-label The base is rebranded to the client’s identity across every surface. 02 ### Deploy Stood up on the client’s own hosting, not ours. 03 ### Publish Apps submitted from the client’s own developer accounts. 04 ### Handover Source, schema, deployment configuration and architecture notes transferred. The client supplies the hosting and domain, a verified developer account we publish from, branding and business details, an onboarded payment gateway with KYC complete, and any third-party API keys. Store review and merchant onboarding are controlled by Apple, Google and the payment provider, so those sit outside our window. [Every figure here is defined on the facts page](https://miracuves.com/facts/#fact-005). ## Who uses it, and for what. Rather than screenshots of a product that has moved on since delivery, this is the set of surfaces that shipped and what each one is for. UbanBank received every one of them, with the source behind each. Every role here is a separate application with its own permissions, its own state and its own release path. Building them to work as one system is most of the engineering in a platform of this kind, and it is the part that was already finished before this engagement began. Customer app accounts, cards, payments Merchant collect, settle, refund Admin KYC review, limits, ## What guards the platform. Built into the base and hardened across every engagement running it, rather than bolted on at the end of this one. Security added late is security that has to be argued for; the controls below were load-bearing from the first deployment. We claim the process, not a certificate. Miracuves does not hold ISO 27001, and we do not say otherwise: we build to the controls those frameworks require, and the evidence trail is there for an auditor who asks. #### settlement collect, settle, refund. Part of the base, so it was proven before this engagement started. #### KYC & AML identity, screening,. Part of the base, so it was proven before this engagement started. #### Role separation Each surface sees only what its role permits, enforced server-side rather than hidden in the interface. #### Audit trail Who changed what and when, retained so a dispute can be answered with a record rather than a recollection. #### Transport and storage TLS end to end, credentials hashed, and anything sensitive at rest encrypted rather than merely obscured. #### Secrets handling Keys live in environment configuration on their own infrastructure, never in the repository we hand over. #### Card data stays out Payment details go to the gateway directly. The platform holds a reference, not a card number. #### What an auditor can actually see We claim the process, not a badge. Everything below was handed to UbanBank with the source. - Commit history for every change in the build window - Environment configuration separated from application code - Database schema with the migration that produced it - Deployment steps written down rather than remembered - Named team and a daily written progress record ## What it connects to. The connection points are part of the base and were already written and tested. Which providers sit behind each one was UbanBank’s decision, because those choices are commercial and jurisdictional rather than technical. This is also where the client-side dependencies live. Gateway onboarding, KYC approval and merchant review are controlled by the provider, not by us, which is why they sit outside the build window rather than inside it. Every one of these was already wired and tested in the base. What changed for UbanBank was which account sat on the far side of it. **Payments and payouts**gateway of their choosing **Identity and KYC**provider per jurisdiction **Object storage and CDN**their bucket, their region **Product analytics**events, funnels, retention **Market data feeds**rates and reference prices **Calendar and scheduling**availability and reminders **Push and transactional email**sent under their sender identity **App store developer accounts**published from their own accounts **Error and uptime monitoring**handed over with the source ## What it runs on. The platform stack for MXNeoBank. This describes the base as it stands today; UbanBank took delivery of the source and has owned it since. **Platform**PHP The stack the MXNeoBank base runs on, already in production elsewhere **Surfaces**Customer appMerchantAdmin Each a separate application with its own permissions and release path **Client decisions**corridorsFee schedulePayment railsBrand & theming Configured for UbanBank during the engagement **Handover**SourceSchemaDeployment configArchitecture notes Transferred at the end of the build ## Where the six days went. Our build time only. Store review and merchant onboarding are controlled by Apple, Google and the payment provider, so they sit outside this window and we do not count them as ours. Stating that plainly is the difference between a build time and a promise we cannot keep. [Every figure here is defined on the facts page](https://miracuves.com/facts/#fact-005). The six working days are guaranteed. If a ready-made platform is not live in six, we keep working free until it is. A deadline nobody is accountable for is not a deadline, and a guarantee nobody pays for is not a guarantee. Throughout, a named team worked the build and sent UbanBank progress on WhatsApp every working day. There was never a week where nobody knew where it stood, which is the part clients tell us they notice more than the date itself. **6 working days** our side of the window The bar below is that window, day by day. Nothing outside it is counted as ours, and nothing inside it waits on someone else. #### What UbanBank supplied A build window only holds if both sides arrive ready. These sat with them, and the clock does not start until they are in place. - Hosting and a domain, on their own account - A verified developer account we publish from - Branding and business details - A payment gateway onboarded, with KYC complete - Third-party keys for the services they chose **Day 1**Base stood up and white-labelled*Base stood up and white-labelled* **Days 2-4**4 client decisions implemented*4 client decisions implemented* **Day 5**Deployed, apps submitted*Deployed, apps submitted* **Day 6**Source, schema and config handed over*Source, schema and config handed over* ## This base has done this before. UbanBank was not the experiment. The base underneath this build had already carried other businesses in other markets before it carried theirs, which is the whole argument for reuse: the risk was retired by somebody else’s project, not by this one. Across everything delivered since 2010 that is more than 9,000 products for over 6,000 businesses across 35+ industries. The eighty-four documented on this site are the ones with a named client and permission to show the work; most of the rest sits under NDA or white-label and is deliberately not here at all. Every number on this page is defined and sourced on a public facts ledger. That is the whole instinct behind how this company is run: most vendors ask you to trust them, and we would rather you checked us. If we cannot back a claim, we do not make it, which is why you will not find a satisfaction percentage or an unnamed award anywhere on this site. **17 of 21** Blocks reused unchanged on this build, each already under load on other engagements. *Architecture* **3** Documented builds running on the Neobank Solution base, in different markets. *Portfolio* **9,000+** Products delivered for more than 6,000 businesses across 35+ industries since 2010. *Company record* **3,900+** Apps published under clients’ own brands, counted per store release. *Company record* ## What the client reported. Figures supplied by the client and published with their name against them. **Deployed in 4 days** reported by the client Ready-made neobank clone, no custom work Ho Pei Aik · Youlife Tecnologia Dell’Informazione S.R.L **6 working days**Our build window on this engagement.Miracuves delivery record **100%**Source code transferred to UbanBank’s own account.Contractual **17 of 21**Blocks reused unchanged from the base.Neobank Solution architecture U > We took the neobank clone as it came. Accounts, KYC and card issuing were already built and proven, we needed nothing bespoke on top, and it was deployed and running in four days. That is why we came back the following year for the Revolut build rather than shopping around again. > > > **Ho Pei Aik**Founder, Youlife Tecnologia Dell'Informazione S.R.L ## What UbanBank holds now. The same on every engagement. What happened to the platform after handover was theirs to decide. *GIT***Application source**Full repository history, transferred to their account*Delivered* *APP***Mobile projects**Sources with signing documented*Delivered* *SQL***Schema and migrations**Reproducible from empty, not a dump*Delivered* *ENV***Deployment configuration**Another team can run it unaided*Delivered* *MD***Architecture notes**What was chosen, what was rejected, why*Delivered* *60d***Support window**Sixty days included, six and twelve month options*Delivered* ## The questions that decide this. Answered for this build. The same answers hold for every Neobank Solution in the portfolio. Do we own the code? Yes. The full repository history transferred to UbanBank’s own account at handover, with deployment configuration and architecture notes. It is not a licence and it is not held against a support contract. How is six working days realistic? Because 17 of the 21 pieces were built and proven before the engagement started. The six days are our build time on that base, not a calendar promise. What sat with UbanBank? Hosting and domain, a verified developer account we publish from, branding and business details, an onboarded payment gateway with KYC complete, and any third-party API keys. Will it look like everyone else’s? No. The base supplies mechanics, not identity. Branding, flows and every customer-facing screen were built for this product. Is this what the platform looks like today? This describes what was delivered in November 2024. What happened afterwards was UbanBank’s to decide; the source transferred at handover. Clients move on, rebuild, or sell up, and none of that changes what was delivered or how it went. Would you have said no to this project? We are a good fit for a founder who wants a proven model launched fast, a deadline they can hold us to, and code they own outright. We are a poor fit for anyone who needs a team embedded in their office full-time, or who wants a blank page and a six-month roadmap. Being straight about that up front saves everyone a call. Who actually worked on it? A named team, not a rotating pool. Our leadership is public with real profiles rather than a stock-photo team page, and progress went to UbanBank on WhatsApp every working day of the build. ## Others on the same base. Different clients, different markets, one proven platform underneath. [**Peter Lu**Neobank Solution - a cross-border neobank](/portfolio/peter-lu/) [**Ryke**Neobank Solution - a Web3 neobank and exchange suite](/portfolio/ryke/) ## Building something like this? Tell us what you are building and we will say plainly whether a ready-made base fits it, including when the answer costs us the larger project. [Book a technical call](https://miracuves.com/schedule-consultation/) [See all case studies](/portfolio/) - Ready-made platform deploys in 6 working days - Custom builds run 2 to 8 weeks - Source code transfers on every engagement - [Every figure here is defined on the facts page](https://miracuves.com/facts/#fact-005) (function(){ var reduce=matchMedia('(prefers-reduced-motion: reduce)').matches; /* read-progress bar */ var bar=document.getElementById('progbar'); if(bar){ var prog=function(){var h=document.documentElement.scrollHeight-innerHeight; bar.style.width=(h>0?(scrollY/h)*100:0)+'%';}; addEventListener('scroll',prog,{passive:true}); prog(); } if(!('IntersectionObserver' in window)) return; /* reveal on scroll */ if(!reduce){ document.documentElement.classList.add('js-anim'); var io=new IntersectionObserver(function(es){es.forEach(function(e){ if(e.isIntersecting){e.target.classList.add('in');io.unobserve(e.target);}});}, {rootMargin:'0px 0px -8% 0px',threshold:.06}); [].forEach.call(document.querySelectorAll('.rv'),function(el,i){ el.style.setProperty('--d',(i%4*80)+'ms'); io.observe(el);}); } /* numeric counters - text metrics are left alone (no data-count) */ /* no count-up on trust figures: it dropped the thousands separator and showed a wrong number while running. The markup already holds the formatted value. */ /* sticky sub-nav scroll-spy */ var links=[].slice.call(document.querySelectorAll('.snav a')); var sio=new IntersectionObserver(function(es){es.forEach(function(e){ if(!e.isIntersecting) return; links.forEach(function(a){a.setAttribute('aria-current', a.getAttribute('href')==='#'+e.target.id?'true':'false');});});}, {rootMargin:'-30% 0px -60% 0px',threshold:0}); links.forEach(function(a){var t=document.getElementById(a.getAttribute('href').slice(1)); if(t) sio.observe(t);}); /* kinetic headline + gantt bars + line reveals */ var kio=new IntersectionObserver(function(es){es.forEach(function(e){ if(e.isIntersecting){e.target.classList.add('in');kio.unobserve(e.target);}});}, {rootMargin:'0px 0px -10% 0px',threshold:.18}); document.querySelectorAll('.kin,.reveal,.gr').forEach(function(el){kio.observe(el);}); /* drag-to-scroll rails + progress thumb */ document.querySelectorAll('.rail,.hstrip,.strip').forEach(function(r){ var down=false,sx=0,sl=0; r.addEventListener('pointerdown',function(e){down=true;sx=e.clientX;sl=r.scrollLeft; r.classList.add('drag');}); r.addEventListener('pointermove',function(e){if(!down)return;r.scrollLeft=sl-(e.clientX-sx);}); ['pointerup','pointerleave','pointercancel'].forEach(function(ev){ r.addEventListener(ev,function(){down=false;r.classList.remove('drag');});}); var thumb=r.parentElement&&r.parentElement.querySelector('.rthumb'), track=r.parentElement&&r.parentElement.querySelector('.rtrack'); if(thumb&&track){ var upd=function(){var max=r.scrollWidth-r.clientWidth,p=max>0?r.scrollLeft/max:0; thumb.style.transform='translateX('+(p*(track.clientWidth-thumb.clientWidth))+'px)';}; r.addEventListener('scroll',upd,{passive:true}); addEventListener('resize',upd); upd(); } }); /* custom cursor */ var cur=document.getElementById('cur'); if(cur && matchMedia('(hover:hover) and (pointer:fine)').matches && !reduce){ var cx=0,cy=0,tx=0,ty=0; addEventListener('mousemove',function(e){tx=e.clientX;ty=e.clientY;},{passive:true}); (function loop(){cx+=(tx-cx)*.16;cy+=(ty-cy)*.16; cur.style.transform='translate3d('+(cx-17)+'px,'+(cy-17)+'px,0)'; requestAnimationFrame(loop);})(); document.querySelectorAll('a,button,summary,.sdev,.hdevice,.rcd').forEach(function(el){ el.addEventListener('mouseenter',function(){cur.classList.add('on');}); el.addEventListener('mouseleave',function(){cur.classList.remove('on');});}); } /* process spine fill + node activation */ var sf=document.getElementById('sfill'), phs=[].slice.call(document.querySelectorAll('.pdeck .phase')), nds=[].slice.call(document.querySelectorAll('.snode')), nls=[].slice.call(document.querySelectorAll('.snl')); if(sf&&phs.length){ var deck=document.querySelector('.proc .pdeck'); var upd=function(){ var r=deck.getBoundingClientRect(),h=r.height-innerHeight*0.5; var p=Math.min(Math.max((innerHeight*0.5-r.top)/(h||1),0),1); sf.style.height=(p*100)+'%'; var act=Math.round(p*(nds.length-1)); nds.forEach(function(n,i){n.classList.toggle('on',i<=act);}); nls.forEach(function(n,i){n.classList.toggle('on',i<=act);}); }; addEventListener('scroll',upd,{passive:true}); addEventListener('resize',upd); upd(); } /* architecture tabs */ var tbs=[].slice.call(document.querySelectorAll('.tb')), pns=[].slice.call(document.querySelectorAll('.tpane')); tbs.forEach(function(t,i){t.addEventListener('click',function(){ tbs.forEach(function(x,j){x.setAttribute('aria-selected',i===j?'true':'false');}); pns.forEach(function(x,j){x.classList.toggle('on',i===j);});});}); /* product screen gallery */ var thumbs=[].slice.call(document.querySelectorAll('.thumb')), shots=[].slice.call(document.querySelectorAll('.shot')); if(thumbs.length&&shots.length){ var show=function(n){shots.forEach(function(x,i){x.classList.toggle('on',i===n);}); thumbs.forEach(function(t,i){t.setAttribute('aria-selected',i===n?'true':'false');});}; thumbs.forEach(function(t,i){ t.addEventListener('click',function(){show(i);}); t.addEventListener('keydown',function(ev){ if(ev.key==='ArrowRight'||ev.key==='ArrowDown'){ev.preventDefault(); var n=(i+1)%thumbs.length;thumbs[n].focus();show(n);} if(ev.key==='ArrowLeft'||ev.key==='ArrowUp'){ev.preventDefault(); var p=(i-1+thumbs.length)%thumbs.length;thumbs[p].focus();show(p);}});}); } })(); /* Everything pinned at the top of the viewport, measured rather than assumed. The theme header is position:fixed and its height is not constant (70px wide, 93px at 1280 where its own nav wraps). When an editor is logged in, the WordPress admin bar sits above it and the header is pushed down, so the top of the window is a STACK of fixed bars, not one. Probing only y=1 finds the topmost bar and nothing else - which pinned the section nav at 32px, directly behind the header, for every logged-in user while looking perfect logged out. So walk down the top edge until we run out of bars and take the deepest. A measurement of 0 means "not found yet" - the theme does not make its header fixed until the first scroll - and must never be written, or it would override the CSS default and pin the nav at the very top. */ (function(){ var scope = document.querySelector('.mcvcs,.mcvhub') || document.documentElement; var nav = document.querySelector('.snav'), last = -1; function measure(){ var h = 0, cx = Math.round(innerWidth / 2), maxY = Math.min(300, Math.round(innerHeight * 0.4)), y, i, e, c, b, found, stack; for (y = 1; y <= maxY; y += 4){ found = 0; stack = []; try { stack = document.elementsFromPoint(cx, y) || []; } catch (err) {} for (i = 0; i innerWidth * 0.6 && b.height > 12 && b.height < innerHeight * 0.4 && b.top = y){ found = 1; if (b.bottom > h) h = b.bottom; } } } if (!found && h) break; // past the bottom of the bar stack } h = Math.round(h); if (!h || h === last) return; last = h; scope.style.setProperty('--site-h', h + 'px'); var navH = nav ? Math.round(nav.getBoundingClientRect().height) : 0; document.documentElement.style.scrollPaddingTop = (h + navH + 14) + 'px'; } measure(); addEventListener('load', measure); var t; function later(){ clearTimeout(t); t = setTimeout(measure, 120); } addEventListener('scroll', later, {passive:true}); addEventListener('resize', function(){ last = -1; later(); }); })();