Scheduling & intake
Appointments, availability, reminders and patient workflows.
CUBE OneCare · Healthcare
One platform with built-in payments for clinics.
CUBE OneCare brings scheduling, records, patient communications, insurance claims and payments into one workflow for private outpatient clinics — in seven languages.
First U.S. clinic pilot implementation underway · First simpleTap production merchant activated
CUBE PlatformIdentity · workflow · AI
communications · payments
communications · payments
CUBE OneCarePilot underwaysimpleTapProduction activated
CUBE AtlasProduct closureHARDWONRefactor
KadoliaRefactor
Assembly + HomePre-build
One platform · product-level gates · no TAM double counting
The first wedge
01 · Front desk
02 · Clinical desk
03 · Unified inbox
04 · Revenue cycle
05 · Money movement
Clinical work and money movement should not live in separate systems.
A private clinic may schedule in one product, manage records in another, submit insurance workflows through another portal, communicate by phone and text, collect payment through a terminal and reconcile the pieces manually. CUBE OneCare connects that path in one operating layer while allowing clinics to adopt modules progressively instead of replacing every system at once.
Records & operations
Clinical and administrative work connected in one operating layer.
Communications
Patient and staff communications tied to the workflow around them.
Claims & eligibility
Clearinghouse-connected insurance workflows, enabled as deployment gates are completed.
Payments & reconciliation
Card and QR payment flows connected to the visit and financial workflow.
Product
See OneCare from the inside.
Working product surfaces in the OneCare experience available today.
CURRENT PRODUCT
SYNTHETIC DEMO DATA
Provider workspace
Scheduling, patient context and operational workflows in the OneCare experience available today.
CURRENT PRODUCT
Scheduling
Appointments, availability and patient workflows connected to the rest of the clinic operation.
CURRENT PRODUCT
Patient & clinical workflow
Patient information, encounters and operational context in one role-based experience.
SANDBOX / SYNTHETIC DATA
Claims & payments
Eligibility, claims and payment flows designed to connect the clinical workflow to reconciliation.
CURRENT PRODUCT
Communications
Patient and staff interactions tied to the workflows around them.
Where we are now
Built software. First implementations. Commercial proof next.
We verify technical readiness and implementation maturity with exact evidence. No premature claims.
CUBE OneCare
PILOT IMPLEMENTATIONOur first U.S. outpatient clinic implementation is underway. The environment currently uses synthetic data and will remain gated from real patient data until the required hosting BAA is executed.
simpleTap
PRODUCTION ACTIVATIONOur first merchant account is activated in production and preparing for its first live transactions.
Product estate
FIVE MATERIALLY IMPLEMENTEDFive CUBE products have material implementation. CUBE Assembly + Home remains pre-build.
Commercial stage
PRE-REVENUEOur immediate milestone is converting the first OneCare and simpleTap implementations into sustained paid usage.
The CUBE platform
Build the hard infrastructure once. Reuse it safely.
OneCare is CUBE's first commercial wedge. Underneath it, CUBE reuses the infrastructure that is expensive to rebuild in every product: identity, permissions, workflows, communications, AI, payments and operational evidence. Reuse does not mean mixing products together. Each product keeps its own customers, launch gates, contracts, evidence and economics.
Commercial focus
Explore OneCare ↗
CUBE OneCare (Dominant Wedge)
Practice operations, clinical workflow, clearinghouse EDI, and patient payments for private outpatient clinics.
simpleTap
Merchant Point of Sale
CUBE Atlas
Financial Orchestration API
HARDWON
Fitness Business OS
Kadolia
Commerce SaaS & POD API
Assembly + Home
Pre-Build Creation Engine
Shared infrastructure rails
Shared CUBE Platform
Identity & permissions
Organizations, users, roles, access and tenant boundaries.
Workflow
States, automation, tasks, approvals and evidence.
Communications
Messaging, voice and workflow-linked interactions.
AI
Model-agnostic intelligence with policy and human release controls.
Money
Payments and financial-provider orchestration through eligible external rails.
Portfolio
One company. Six focused products. One shared platform.
The portfolio is a sequence — not six simultaneous launches.
NOW · First Pilots & Activations
CUBE OneCare
PILOT IMPLEMENTATIONHealthcare operating platform
Practice operations SaaS for private outpatient clinics and independent physicians. Software licenses + clinic patient pay via Stripe Connect.
simpleTap
PRODUCTION ACTIVATIONMerchant payments and operations
Designed as a generic NFC point of sale for Android, direct to merchants: in-person contactless, QR and payment-link acceptance.
NEXT · Closure & Refactors
CUBE Atlas
PRODUCT CLOSUREFinancial orchestration API
CUBE's unified API for financial orchestration and its ledger, on the same Stripe platform. Sandbox; no live money yet.
HARDWON
MARKET-FACING REFACTORFitness business operating system
Fitness management, memberships, and facility scheduling requiring launch QA.
Kadolia
MARKET-FACING REFACTORCommerce SaaS · Print-on-demand API
A commerce SaaS with a unified print-on-demand API (white-label storefronts on a POD network). In development; not live and not onboarding connected accounts.
LATER · Future R&D
CUBE Assembly + Home
PRE-BUILDSoftware creation and cross-product account
CUBE Assembly is what we're building for people who build software. Ask CUBE is what we're building for everyone who uses CUBE. It's pre-build, and CUBE is its first customer.
Footnote: Each product must earn commercial proof independently. Shared technology does not substitute for product-level evidence.
Engineering
Founder-built. AI-accelerated.
Felix Parentini, CUBE's co-founder and CTO, leads architecture and directs CUBE's AI-assisted engineering. CUBE builds with modern AI capabilities across multiple model families, maintaining founder-directed architecture and human release authority over every deployment. Every release must satisfy deterministic acceptance criteria before shipping.
Model independence
We evaluate and utilize multiple frontier model families instead of tying engineering to a single vendor.
Continuous validation
Deterministic test coverage, strict regression gates, and automated validation across every repository.
Human release authority
AI accelerates implementation throughput. Architecture, acceptance criteria, and final release decisions remain under founder control.
Trust boundaries
Built for regulated workflows without pretending unfinished work is finished.
We maintain strict segregation between clinical and financial rails and state regulatory status transparently.
HIPAA & BAA Architecture
Built for HIPAA from day one: our clearinghouse BAA is signed, and our hosting BAA will be signed before any real patient data enters the platform.
Data segregation
Clinical data stays in CUBE OneCare; payment systems receive only payment data. Real patient data remains gated until the required hosting BAA is in place.
Interoperability
Interoperability capabilities (FHIR R4/SMART) are in development; production runtime is enabled only when deployment requirements are satisfied.
Certifications and attestations belonging to infrastructure providers are not presented as CUBE certifications.
Why CUBE can compound
OneCare is the wedge. CUBE is the platform underneath it.
Healthcare is where CUBE is concentrating its first major vertical go-to-market. The infrastructure underneath OneCare can also support payments, financial services, fitness and commerce without rebuilding identity, workflows, communications, AI and transaction infrastructure from zero.
Over time, clinicians will be able to create their own modules without code, developers will build on the platform, and approved modules can move through a curated exchange — only after the underlying product earns real commercial proof.
Founders
Three founders. Clear accountability.
Complementary leadership directing product execution, engineering, and financial structure.
Danny Elreda
Co-Founder & CEOLeads CUBE's commercial strategy, partnerships and fundraising.
Felix Parentini
Co-Founder & CTOLeads architecture and directs CUBE's AI-assisted engineering.
Israel Cueva
Co-Founder & CFOLeads finance, capital structure, reporting and Latin American operations.
For investors
Go deeper into the CUBE thesis.
Review product maturity, the shared technology platform, portfolio sequencing, economics, roadmap and current financing materials.
Start with the product.
Contact
Tell us what brings you here and we will route your message to the right team. We reply in 2-3 business days.