Auth, data, files, functions, messaging, and rule-bound autonomous accounts. One API. Any chain.
A chain-agnostic backend that proves every operation on-chain — no smart contracts, no gas, no per-chain rewrites. Pick the trust level for each account: co-signed with the network, or network-only.
You've had to pick one: Firebase-grade DX or blockchain-grade trust. The easy tools centralise everything; the trustless ones demand Solidity, gas, and per-chain rewrites.
New SDK, new wallet model, new gas token, new contract language per chain. Going multi-chain means rewriting the app each time.
Users pay unpredictable gas in a token they don't hold. Most "web3 apps" quietly abandon decentralisation at the first sign of friction.
A public attack surface that lives forever. Six-figure audits. One bug drains the funds in minutes — no rollback, no recourse.
Most providers store your data centrally and call it trustless. Firebase with a blockchain logo. You're still trusting one company.
Smart Engines gives you a normal backend API where the blockchain does the work no backend can: prove it, refuse to cheat, and let the user stay sovereign.
A cryptographic proof on every write — automatically.
Every operation emits a Merkle proof anchored on-chain in seconds. Your data lives in a fast database; its integrity is guaranteed by the chain.
No Solidity. No gas. The network is the contract.
The validator network handles all on-chain interaction. You never write, audit, or deploy a contract. Full trustlessness, no Solidity PhD.
Two signing modes — pick the trust level per account.
Either you co-sign with the validator network, or the network signs alone. You choose per account, and the network enforces that choice cryptographically every time.
Every request takes the same path. For Smart-Agent actions the network checks the account's on-chain rules first — and refuses anything that breaks them.
A standard REST or SDK call. Feels exactly like any modern backend — no blockchain knowledge required.
POST /api/v3/db/insertThe validator quorum checks on-chain rules (for Smart-Agents), then co-signs via threshold signature. Rule violations are refused.
rules ✓ · TSS quorum ✓The Merkle root is anchored on your chosen chain. Immutable, timestamped, independently verifiable.
txId: 0xabc…def ✓You receive a Merkle proof — verifiable evidence the operation happened exactly as recorded. No trust required.
merkleProof: "0x…" ✓Each cluster runs five services. For the curious — everything above is built on these.
The only service on the public internet. Routes traffic to the in-cluster validator and host.
Holds one DKG keyshare, runs the Rules Engine, joins ABFT consensus. Never sees the full key.
Runs deployed smart-apps plus the BaaS data plane: db, storage, messaging, functions.
Provisions whole clusters from declarative input — helm, k8s, genesis, upgrades.
Permissionless entry for new operators. Issues certs, maintains the host registry.
One DKG ceremony derives native threshold keys per chain. No wrapped tokens, no bridges — transactions look identical to any other signed tx on that chain.
HederaXRPLPolkadotSolanaStellarBitcoinCardanoByzantine fault-tolerant TSS consensus, multi-chain anchored. Showcase smart-app deployed.
External security audit, mainnet, Polkadot + Solana rollout, production SLA.
Permissionless validator onboarding opens — run a node, earn HSUITE for validation work.
Install the CLI, register your appId, write your first Merkle-proof-anchored record. Smart-Apps for full applications, Smart-Agents for rule-bound autonomous accounts.