The data that can't leave
can still be put to work.
Confidential documents and the keys that move assets both stay unused for the same reason: they cannot be handed to an outside service. We design, build and operate systems that keep them inside your perimeter.
Where the enquiries come from
What they have in common is a constraint: the information involved cannot be sent outside the organisation.
Manufacturing
Drawings, specifications and past incident reports. Confidentiality obligations to customers often rule out external transmission entirely.
Healthcare
Records containing patient information, where Japan's three-ministry guidelines shape what any deployment can look like.
Finance & payments
Identity records, transaction histories and key custody, in businesses that must answer to a regulator.
Public sector
Work involving resident data, where network separation requirements assume a closed environment from the outset.
Professional services
Client contracts and filings held under professional confidentiality obligations.
Web3 & digital assets
Wallet infrastructure, custody and KYC/AML, designed for production rather than demonstration.
On-premise generative AI platforms
Between the department that wants to use generative AI and the IT function that cannot approve outbound data, projects stall. We build deployments where the data, the model and the logs all stay inside — from design through to adoption.
Nothing to explain about where data goes
When outbound transmission is prohibited by internal policy or by contract, an assurance that inputs aren't used for training does not get a proposal approved. If nothing physically leaves, no such assurance is needed.
Logs that survive an audit
Who entered what, and which documents produced the answer. For firms serving healthcare, finance or the public sector, where those records sit is the question that gets asked.
Cost that doesn't scale with use
Per-token pricing makes organisation-wide rollout impossible to budget. Owned infrastructure fixes cost at capital plus operations, which removes the reason to ration internal use.
Design and build
We size GPU capacity from your intended use and concurrent users, then build a closed environment in your own rack or data centre. No lock-in to any single model vendor.
Search over internal documents
We prepare your existing policies, manuals, past projects and drawings so the system can cite them when answering, and we carry your existing departmental access rights through unchanged.
Operations and adoption
The most common failure is a system that is delivered and then never used. We hand over runbooks and run training for the people who will actually use it.
This service is delivered under a Business Innovation Plan approved by the Governor of Tokyo in June 2026. Because the plan has been through review, we can help you build a deployment plan around available subsidies and grants — including at the stage where budget has not yet been secured.
Three things worth checking in any vendor
Plenty of firms can get something working. The difference shows up afterwards.
Designed for custody
Confidential documents and private keys sitting unprotected on a server leave you with nothing to say when something goes wrong. Isolation and separation of duties belong in the design from the start.
Built to leave a trail
Who approved what, and what was executed as a result. Without a record you can follow after the fact, neither an audit nor an internal report holds up.
Not finished at handover
Model updates, protocol changes, library maintenance. We deliver the procedures for the things that will certainly happen after go-live.
Blockchain and digital asset systems
The difference between a project that ends at proof-of-concept and a system that moves real money is how the keys are held and how it is operated. We take design, key management, regulatory fit and handover as a single scope of responsibility.
Advisory and technology selection
We start from whether a process belongs on-chain at all. Cost modelling and the material you need for internal approval are included.
Smart contract development
Specification through implementation, testing and deployment, with code and documentation prepared for third-party audit.
Payment and DeFi infrastructure
Aggregating deposits and withdrawals across chains and currencies, with rate handling and balance reconciliation that your accounting team can tie out.
Wallets and custody
Key generation, storage and signing built so that no operator ever touches a private key. Approver separation, transaction limits and emergency stop are part of the design.
KYC / AML
Identity verification and transaction monitoring built into the operational flow, with retention periods and reporting formats designed for regulatory examination.
NFTs and GameFi
Issuance and circulation of digital assets, and in-game economic design — with post-launch running costs and secondary markets accounted for from the beginning.
- Ethereum
- Polygon
- Arbitrum
- BNB Chain
- Solidity
- Hardhat
- AWS KMS
- HSM
- Multisig
- ERC-20
- ERC-721
- The Graph
- KYC / AML
- Chainalysis
- Uniswap v3
- Ledger
- Ethereum
- Polygon
- Arbitrum
- BNB Chain
- Solidity
- Hardhat
- AWS KMS
- HSM
- Multisig
- ERC-20
- ERC-721
- The Graph
- KYC / AML
- Chainalysis
- Uniswap v3
- Ledger
Our own product
What we learn on client work also goes into a product of our own.
LPBot
Position management for DEX liquidity providers
A tool for people providing liquidity on decentralised exchanges such as Uniswap. It watches your price range, rebalances positions according to conditions you set, and reports back through a Telegram bot.
About LPBotBefore you use it
- Digital asset prices move sharply, and you may end up with less than you put in.
- Providing liquidity carries impermanent loss. If fee income does not exceed it, your position loses value.
- The tool executes conditions you configure. It does not forecast markets or prevent losses.
- Use is at your own discretion and risk.
How engagements start
You do not need settled requirements to talk to us. Working out what should be built is often where we start.
First conversation
What information you want to work with, your existing systems, and the internal constraints. Thirty minutes online is enough to begin.
Scope and estimate
Architecture, scope, timeline and cost, set out in writing. Everything up to this point is free of charge.
Design
Data handling, key and permission design, and external integrations, agreed as a written specification.
Build and validation
Running it for real on a limited scope, confirming accuracy and fit before moving to the production configuration.
Go-live and operations
Monitoring, runbook handover and user training, with ongoing maintenance available.
Company
Based in Toshima, Tokyo, building systems for organisations that handle sensitive information. Our background in the Chinese internet industry informs how we implement within Japan's regulatory environment.
| Name | IXPERT Inc. (株式会社アイテック) |
|---|---|
| Representative | Nanhou Tei, Representative Director |
| Address | Citio Otsuka 101 1-22-12 Kita-Otsuka, Toshima-ku Tokyo 170-0004, Japan |
| Phone | +81 3-6630-8360 |
| contact@ixpert.co.jp | |
| Services | On-premise generative AI platforms; blockchain and digital asset system development; smart contract development; IT consulting |
| Accreditation | Business Innovation Plan, approved by the Governor of Tokyo (June 2026) |
| Tax registration | Qualified invoice issuer T4012401041345 |
Tell us what you're trying to do
You don't need to have decided on anything. We're happy to look at feasibility alone.
- contact@ixpert.co.jp
- TEL
- +81 3-6630-8360
- ADDRESS
- Citio Otsuka 101
1-22-12 Kita-Otsuka, Toshima-ku
Tokyo 170-0004, Japan