JunleeBuild
Contact
← Back home

JUNLEEBUILD / PRODUCTS

What are we building?

Find out who each tool is for, how to use it, and how it works underneath.

01 / AI spending and services

AgentPay Lite

Decide where AI can spend, and how much.

Choose which services your team can use and set a budget before anyone spends. API sellers can list their services, set prices, and keep receipts together.

  • Team spending limits
  • API listings and prices
  • Usage and receipts
Visit productLearn more
What’s been built
  • Budgets and service choices for each accountReady
  • API listings and prices for sellersReady
  • Paddle payment servicesPaddle approved
Explore the features
01 / BUDGETS & ACCESSFeature overview
Per-use limitDaily limitMonthly limit

A diagram explaining the product's features.

Technology & architectureCheck the limit. Approve the payment. Verify the result.x402 v2 ProtocolBase · USDCEIP-3009Permit2Cryptographic ReceiptsExplore the architecture
Architecture flow

How it works, in three steps

Connect each AI service call to its budget and payment terms. Preparation, wallet approval, delivery, and receipt verification follow one execution record.

  1. Quotes bind price, recipient, and network. A changed budget or service configuration stops the existing approval path; USDC amounts use integer microunits.

HTTP 402 · Budget guard

Quotes bind price, recipient, and network. A changed budget or service configuration stops the existing approval path; USDC amounts use integer microunits.

Built into the design

Security & design principles

Signing stays with the user
Non-custodial authorization

Approval comes from the connected wallet or passkey. The server checks the approved terms without signing on the user's behalf.

Recover without duplicate execution
Idempotency · Reconciliation

A request, signature, and settlement transaction belong to one execution. Connection failures after approval are resolved against the existing record.

Protected seller connections
Encrypted upstream credentials

Upstream URLs and API keys are stored in an encrypted record. Public service listings provide the AgentPay gateway URL.

02 / Document and code review

AEROS

Find what needs a closer look.

Redact personal details, review contract terms, and check code for risks. Download the results and a record of the review.

  • Personal data redaction
  • Contract and code review
  • Result and receipt downloads
Visit productLearn more
What’s been built
  • One place to review documents and codeReady
  • Downloadable results and review recordsReady
  • Paddle payment servicesPaddle approved
Technology & architectureMask sensitive details. Keep the review record.Rust · WebAssemblyLocal ModelsSHA-256 ReceiptsAzure AttestationGroth16 · BLS12-381Explore the architecture
Architecture flow

How it works, in three steps

Choose personal-data masking, document review, or code review in one workspace. Download the result and check which policy and model were used.

  1. NFKC normalization precedes email and explicit API-key matching. Korean identifier date and checksum checks, plus the Luhn card check, determine the masking scope.

Rust · WebAssembly

NFKC normalization precedes email and explicit API-key matching. Korean identifier date and checksum checks, plus the Luhn card check, determine the masking scope.

Built into the design

Security & design principles

Encrypt for a checked environment
Azure MAA · X25519 · AES-GCM

A separate masking SDK verifies Azure evidence before encrypting input. Ordinary document review follows a path without hardware attestation.

Keys and evidence bound to a request
Request binding · Replay protection

The attested key, request, and tenant are bound together with expiry and replay checks. Verification also covers Azure signatures, VM identity, and the request-bound vTPM quote.

Computation proofs with a defined scope
Groth16 · Aptos Move

A separate engine proves an incorrect claimed sum of four integers from 25 to 99. Current records use Aptos localnet, TestUSD, and a single-party setup.

03 / VRChat gatherings and entry

VR-Gate

Bring people together. Decide who can find the room.

Put a room on your profile or share it only with invited guests. Use a PIN or a unique VIP ticket for entry, and choose how widely each gathering is shared.

  • Public profiles and private links
  • PINs and unique VIP tickets
  • World discovery and Creator Studio
Visit productLearn moreOfficial X
What’s been built
  • Let creators choose room visibility from their profilesLive
  • Made PIN, VIP and room controls easier to useLive
  • Improved world search and image loadingLive
  • Paddle payment servicesPaddle approved
Technology & architectureChoose who can see the gathering and how they join.Sharing controlsSingle-use admissionWindows · QuestHybrid searchExplore the architecture
Architecture flow

How it works, in three steps

Connect world discovery, creator-controlled sharing, single-use admission and the right VRChat launch path for each device.

  1. Keyword and semantic search find candidates, then current records confirm visibility, capacity and Quest support. Profile listings and admission credentials are managed separately.

Hybrid search · Creator profile

Keyword and semantic search find candidates, then current records confirm visibility, capacity and Quest support. Profile listings and admission credentials are managed separately.

Built into the design

Security & design principles

Separate sharing from admission
Profile visibility · PIN version

Creators choose profile listings or direct links without a global room directory. A PIN change invalidates unused general tickets and older re-entry credentials.

Prevent token reuse
PostgreSQL row lock · Redis atomic consume

Admission tokens are hashed and consumed atomically. Short re-entry links also use one atomic Redis read-and-delete operation.

Recheck current world records
Hybrid retrieval · Revalidation

Cached search results are checked against current world state. Request coalescing, budgets and local search fallback handle external search delays.

05 / Streaming audio and clips

CasterDesk

Shape your sound. Save the moment.

On Mac, clean up your mic and let background music dip when you speak. Save the last 15 or 30 seconds as a clip.

  • Noise reduction and voice filters
  • Music that dips when you speak
  • 15- and 30-second clips
Visit productLearn more
What’s been built
  • Mac microphone and virtual cable connectionChecked
  • Music that lowers itself when you speakReady
  • Video clips with captionsChecked
Technology & architectureFrom microphone to broadcast to clip.Rust · TauriDeepFilterNet3 LLRNNoiseWhisper · SileroExplore the architecture
Architecture flow

How it works, in three steps

Noise reduction, broadcast mixing and captioned clips follow one connected audio path.

  1. Tract processes 480-frame model hops before dereverberation and voice filters. A dedicated worker keeps neural computation separate from device callbacks.

48 kHz · DeepFilterNet3 LL · RNNoise

Tract processes 480-frame model hops before dereverberation and voice filters. A dedicated worker keeps neural computation separate from device callbacks.

Built into the design

Security & design principles

Keep callbacks lightweight
Bounded SPSC · Preallocated buffers

Device callbacks use preallocated memory and atomic state. Bounded queues connect them to the separate neural worker.

Local audio, separate GPU speech
Rust / Tract CPU · CUDA / TensorRT

Microphone, music and clips run locally. Optional CosyVoice3 synthesis uses an authenticated GPU server, with recorded responses from Azure T4.

Hardware-specific paths
Apple Silicon · macOS 26+

Mac virtual-cable output and captioned clips have been checked. Windows and RTX hardware, encoder compatibility and total latency targets remain under validation.

Paddle

Payments

Payments for AgentPay Lite, AEROS and VR-Gate are processed by Paddle. See each product for pricing and terms.

CONTACT

Let's talk about the products.

Send an email