Get started in 5 minutes.
One SDK. Nine services. Any chain. Smart-Apps fit into your existing stack, REST endpoints, TypeScript SDK, OpenAPI / Swagger docs. No onboarding calls, no vendor lock-in.
Quick start From
From npm install to live smart-app
Five commands. The CLI handles wallet generation, faucet funding, on-chain registration, and deployment. You don't talk to the chain directly once.
terminal
# 1. Install the CLI globally (Node 20+)
npm install -g @hsuite/smart-engines-cli
# 2. Initialise: writes a fresh .env.local with an XRPL testnet
# wallet, auto-funded with testnet XRP. All local; nothing to commit.
hsuite init
# 3. Drip HSUITE (HST) testnet tokens to your dev wallet. Sets the
# HST trustline automatically if you don't have one yet.
hsuite faucet
# 4. Subscribe your smart-app: pays the HST deposit, mints your
# subscription NFT, and binds a real appId. Free on testnet.
hsuite subscribe
# 5. Deploy a smart-app from a JSON manifest (init → push → deploy).
hsuite deploy --manifest ./smart-app.manifest.json
# 6. Install the SDK in your app:
npm install @hsuite/smart-engines-sdkReal SDK
One client. Nine services.
The TypeScript SDK exposes one BaasClient with nine sub-clients, .customerSession, .db, .storage, .functions, .messaging, .agents, .rules, .entities, .deployment. Same auth, same response shape, same Merkle proof on every write.
Full TypeScript support with strict types OpenAPI / Swagger docs for every endpoint Pure REST API, no SDK dependency required Chain-agnostic, swap chains without code changes Merkle proof returned on every write Two sovereignty modes, pick who signs Permissionless validator network, anyone can run a node No gas, no Solidity, no smart-contract audits
auth.ts
// Customer-session login, any supported chain.
import { BaasClient } from '@hsuite/smart-engines-sdk';
const baas = await BaasClient.connectToCluster({ network: 'testnet', appId });
// 1. Ask the host for a one-time challenge
const { challenge } = await baas.customerSession.challenge({
chain: 'xrpl',
address: wallet.address,
});
// 2. Sign with the user's wallet, private key never leaves the device
const signature = await wallet.signMessage(challenge);
// 3. Submit → short-lived JWT (≤15 min TTL), session metadata
const { token, sessionId, expiresAt } = await baas.customerSession.verify({
appId: baas.getAppId()!,
chain: 'xrpl',
address: wallet.address,
publicKey: wallet.publicKey,
signature,
challenge,
});Reference implementation
See one running.
The showcase is a full smart-app: backend, frontend, and SDK examples, deployed on the Smart Engines validator network. Read its architecture, run it locally, fork it.
Smart-Apps vs smart contracts
Why a contract can't do this.
A smart contract is code on a single ledger, no keys of its own, no files, no off-chain compute, no sessions, no other chains. Smart Engines give Smart-Apps the missing primitives.
Hold its own keys
A contract has no key. It can't sign an outbound tx, can't talk to another chain, can't custody anything except its own state slots.
TSS / DKG threshold signatures
The keyset is the validator network. Smart-Apps sign their own transactions on Hedera, XRPL, Solana and Polkadot from one logical identity.
Store files or blobs
Contract storage is bytecode + state slots. PDFs, JSON manifests, images, ML weights, none of it fits.
BaaS storage with Merkle proofs
IPFS for blobs, MongoDB for structured data. Every write returns a Merkle proof anchored to Hedera HCS, auditable forever.
Run off-chain compute
A contract can't call an LLM, hit an HTTPS API, run an ML model, or parse a PDF. The VM doesn't allow it.
Smart-Host Functions
TypeScript / WASM functions run on the validator network. Schedule them, invoke them, return verifiable output.
Maintain sessions or identity
Every contract call is stateless. No logged-in user, no auth flow, no rate limiting, no rotation-safe identity.
Customer-Session + TSS-signed JWTs
Sign a one-time challenge with your wallet, get a short-lived JWT. Identity survives validator churn via DKG resharing.
Operate across chains
A Solidity contract is an Ethereum contract. An XRPL ledger object is an XRPL object. Each chain is an island; bridges are not the answer.
One identity, every chain
TSS keys are derived natively for each chain from the same threshold ceremony. No bridge. No wrapped token. No 40-minute finality.
What's possible
Six patterns you could build today
Concrete shapes that map to the primitives above. Each card describes the pattern, the services involved, and why it doesn't fit a contract.
01
Cross-chain AI trading & treasury agents
An autonomous agent operates one logical treasury spanning Hedera, XRPL, Solana and Polkadot. LLM decision logic runs as a Smart-Host Function; every outbound tx is authorized via TSS so no node ever holds the key.
02
Regulated stablecoins with compliance-in-the-signing-path
Every mint / transfer passes through the Rules Engine that calls real KYC providers, geo-allowlists, sanctions feeds and velocity limits before the validator quorum will TSS-sign.
03
Verifiable-state BaaS, journalism, records, audit logs
Structured data in MongoDB, blobs in IPFS, every mutation emits a Merkle proof anchored to Hedera HCS. Full product UX, search, auth, real-time updates, with cryptographic auditability.
04
Sovereign SSO & passwordless identity
JWTs signed via TSS, the signing key is a threshold share held by validators. Users rotate credentials, validators come and go via DKG resharing, yet the on-chain identity remains stable.
05
Decentralized hosted SaaS & verifiable CDN
Smart-Apps content-addressed (IPFS CID), deployed across Smart-Hosts, discovered via Smart-Gateway DNS, served over HTTPS. Hosts prove liveness; bad hosts are reputation-slashed.
06
Post-quantum notary & long-horizon archival
Every DKG ceremony produces both classical BLS12-381 and post-quantum Dilithium keys. A notary Smart-App co-signs attestations with both, publishing anchors to HCS, verifiable decades from now.
Build a smart-app this week.
Install the CLI. Run hsuite init. Read a page of docs. Deploy. Watch the network anchor your first proof on-chain.