Product & technical overview
Enter your work email to download the PDF. You’ll get the same confirmation and updates emails as our site newsletter (with opt-out in the message).
AirLiftLab builds dollar-first products on USDC: Pay & Store for everyday send and secure storage, and StablePay for global payouts and invoicing-style workflows. Execution favors Arbitrum L2; Ethereum provides settlement and security assumptions users should not have to think about.
Consumer & small and medium-sized businesses (SMB)
Pay & Store is where people and small teams send stable value, see costs in familiar dollar terms, and keep files protected behind encryption and clear access rules.
The experience is built for daily use: balances, transfers, and storage tiers without asking users to become chain specialists.
USDC on Arbitrum handles execution speed; Ethereum carries the settlement story enterprise buyers already recognize.
Payouts & operations
StablePay is built for finance and operations teams that need repeatable stablecoin payout runs, collections context, and fewer manual wiring steps.
Workflows stay dollar-first in the UI so approvers see amounts, fees, and statuses they can defend in audit.
The same USDC, Arbitrum, and Ethereum stack backs execution and settlement, so operators get speed without improvising a new chain strategy per corridor.
Global users and businesses need to move and hold value in stable USD without becoming protocol experts. Three drivers match what we build:
USDC aligns what users see in the product with how value actually moves on-chain, which reduces surprise when fees and settlement are discussed.
Stablecoins are the practical bridge between bank-era UX expectations and verifiable settlement.
That choice keeps positioning honest: we are not training customers on a bespoke unit of account to use basic features.
Teams need invoicing, collections, and global payout runs with line-item clarity instead of opaque wire batches.
Operators should be able to replay who approved what, when funds left, and what fees applied.
StablePay is aimed at that discipline: fewer manual handoffs and a consistent stable USD rail.
Arbitrum keeps user-visible transfers fast enough for real workflows without dominating cost.
Ethereum remains the settlement layer institutions already reference in diligence and onboarding.
Together they give a clean story: speed where users interact, seriousness where policy and finality matter.
AirLiftLab is a multichain Web3 platform for stablecoin-native products—built on USDC with Arbitrum execution and Ethereum settlement—and delivered through web and mobile experiences with the same dollar-first design. Three capabilities map directly to customer value:
Pay & Store combines send, receive, and file storage so individuals and small and medium-sized businesses can treat stable USD as an everyday rail.
Fees and balances are presented in dollar terms wherever possible to match customer mental models.
Open Pay & Store from the link at the top of this page on the web or on your phone—same product, responsive layout.
StablePay packages invoicing, collections context, and payout runs for operators who live in approvals and audit trails.
The goal is one-click execution for well-defined batches once policy checks pass.
Teams adopt it when they want stablecoin treasury motion without rebuilding finance stack from scratch.
Files are protected with end-to-end encryption; content addressing follows IPFS-style CIDs for integrity.
Retention follows four product tiers—from time-bounded trial pinning through 0G Storage and Arweave—so teams pick speed and durability without hand-tuning networks.
Sharing and access changes are governed by product policy and cryptography together, not by informal side markets.
End-to-end paths through the live products—how someone actually finishes a task before any stack detail.
Individuals & small and medium-sized businesses (SMB)
Sign in
Land on a dollar-first home: balances and next actions read like everyday banking, not a raw wallet.
Pick a storage tier
Choose Free, Standard, Pro, or Enterprise so retention and access speed match the job—then upload with encryption on by default.
Organize & share
Folder-style workflows; optional time-bound shares with clear view/download rules and minimal repeated signing.
Pay or get paid in stable USD
Send USDC or accept a payment with amounts and fees quoted in dollars; confirmations reflect fast L2 execution.
Receipt & history
Activity and file events stay reviewable in-product for ordinary troubleshooting and light audit.
Finance & operations
Onboard the operator context
Roles, payout templates, and references (e.g. invoice IDs) so batches are repeatable week to week.
Compose a payout run
Line up recipients and USD-denominated amounts; validate totals before anyone approves.
Approvals & policy
Reviewers see the same dollar table; the product records who cleared which step for later replay.
Execute in one action
When gates pass, dispatch USDC payouts on Arbitrum with Ethereum-aligned settlement assumptions.
Receipts & close
Statuses, exports, and history support reconciliation—without rebuilding spreadsheets per corridor.
For a narrative walkthrough with personas, see the use case page.
Our architecture is our primary defensible moat, designed for security, scalability, and user experience without compromise. It consists of an execution layer, a storage layer, and a settlement layer.
Ethereum is our settlement and security anchor. Batched or bridged state from Arbitrum ultimately inherits Ethereum’s consensus guarantees. Liquidity and integrations for USDC leverage the standard Ethereum ecosystem (DEXes, custody, on-ramps). Pay & Store and StablePay are designed to run on USDC with fees and balances surfaced in dollar terms.
Day-to-day value movement and workflow orchestration are built around USDC on Arbitrum and Ethereum settlement. Users interact through the two product surfaces described above—one experience for storage and pay, another for operator-scale payouts.
Arbitrum hosts the contracts and transfers end users feel day to day.
Fees stay compatible with habitual use rather than ceremonial settlement.
Both Pay & Store and StablePay lean on this layer for USDC movement.
Pay & Store concentrates balances, storage, and consumer-grade flows.
StablePay concentrates approvals, batches, and treasury-style operations.
Both hide chain trivia behind product language and consistent dollar cues.
Encrypted objects and metadata follow least-privilege rules the product can enforce.
Tiered storage trades off access speed, retention policy, and durability per workload.
Controls stay explicit so security review can trace intent to implementation.
Four tiers match how long data must live and how fast you need it back—using IPFS for short-lived trial space, 0G Storage for everyday decentralized persistence, and Arweave where permanence or immutability matters.
Typical journey → tier choice
Trial · IPFS · 5 GB
For new users who want to try uploads and flows without a long-term commitment.
Data rides on IPFS-style temporary pinning—fast to use for exploration.
After a fixed retention window (90 days), objects age off automatically—think guided trial, not archive.
Active work · 0G Storage · 50 GB
For teams shipping day-to-day files and collaborations that should stay put until you delete them.
Payloads live on 0G Storage, a decentralized network tuned for routine upload and download.
No automatic expiry: objects remain while the account and policy allow—ideal for ongoing projects.
Hot + permanent · 0G + Arweave · 200 GB
For assets you touch often today and still need provably preserved tomorrow.
New writes land on 0G Storage for responsive access; the system automatically mirrors to Arweave for permanence.
An initial window favors fast retrieval; later reads lean on Arweave—slightly slower, built for long-horizon safety.
Immutable vault · Arweave · 500 GB
For legal, IP, or compliance records that must not vanish or be rewritten casually.
Objects go straight to Arweave with broad miner replication and immutability suited to audit.
Once committed, data follows Arweave’s permanent semantics—strongest option when loss or silent change is unacceptable.
Advanced workflows—shared file access, approvals, and payout runs—are designed to stay dollar-first in the product. Cryptographic controls, encrypted storage, and application policy enforce who can do what; the exact mix of on-chain and off-chain verification follows what each product surface ships (Pay & Store vs StablePay).
The user chooses an action in-app (for example, grant time-limited view access, or trigger a payout run).
AirLiftLab validates identity, permissions, and compliance with the request using the product's security model (including smart-contract logic where deployed).
For files: encrypted access is granted only to verified recipients. For money: stablecoin movement is executed on Arbitrum with settlement tied to Ethereum as described above.
AirLiftLab operates as a company shipping regulated-grade software. Progressive decentralization or community governance may apply to specific protocols or assets in the future and will be documented when relevant to users and investors—separately from day-to-day product terms.
Product and infrastructure decisions prioritize safe rollout of Pay & Store and StablePay on Arbitrum/Ethereum.
Security, incident response, and compliance work alongside public documentation and investor materials (e.g. Business Model, Data Room).
Material changes to products or policies are communicated through updated documentation, security notices, and terms customers can rely on.
Today’s economics are built around USDC and standard subscriptions and usage fees.
Figures below mirror internal planning materials on the main site; they are not guarantees. The live stack is USDC · Arbitrum · Ethereum plus encrypted storage tiers.
Users (base-case Year 5, model)
Illustrative valuation (base case)
Settlement stack for shipped products
Quarters are indicative. Scope concentrates on Pay & Store and StablePay on the USDC, Arbitrum, and Ethereum stack.
Ship reliability and clarity for both retail-style storage or pay and operator payouts.
Keep USDC motion on Arbitrum predictable while Ethereum remains the settlement reference.
Use the dedicated product buttons at the top of this document when you want to open either environment.
Deepen encryption coverage, tier behavior, and audit trails so enterprises can adopt with confidence.
Layer regional and regulatory packaging where payout customers require documented controls.
Treat compliance as product surface area rather than an appendix.
Add destinations, dashboards, and automation so recurring finance work stops being bespoke engineering.
Preserve one-click batch ethics: review, approve, then execute with receipts.
Expand only where treasury teams ask for measurable time saved.
Partnerships and on-ramps enter only when they simplify customer outcomes, not when they complicate narrative.
Integrations ship with documented roles, data flows, and support ownership so operators know who runs each piece.
Scope expands when there is measurable reliability and time saved for finance and operations teams.