The way developers build is changing. AI-assisted workflows are becoming more common, teams are moving faster, and expectations for developer tools are higher. Libraries need to be easier to work with, safer to use, and better suited for the path from prototype to production.
AlgoKit 4.0 is the umbrella for the next set of improvements to the Algorand developer experience.
The first step is the beta release of AlgoKit Utils for TypeScript and Python, a major update to the core libraries developers use every day.
What's new at a glance
This AlgoKit Utils beta includes:
- One unified AlgorandClient: a single entry point for transactions, accounts, assets, apps, and state, with the same shape in TypeScript and Python
- Signer-based accounts: no more raw private keys in application code, designed to integrate with cloud KMS, HSMs, and other secure key stores
- HD wallets built in: one seed, unlimited derived accounts, with first-class support in TypeScript and the primitive now shipping in Python
- A more consistent API: chainable transaction construction, standardized naming, and stronger typing (typed Address objects and bigint IDs in TypeScript)
- ARC-56 by default: automatic conversion for existing ARC-32 specs
- No direct algosdk dependency: AlgoKit Utils now provides the core clients, types, and utilities through its own packages and subpath exports
Wallet and key management built for production
As more teams bring Algorand applications into production, account and key management become more important. That's why the libraries now ship with a signer-based account model in both languages, so application code works with signing functions, not raw private keys. Accounts loaded from .env files are still supported for local dev and quick scripts, but production apps now have a more secure default.
Alongside that, the library is designed to integrate with cloud KMS, HSMs, and other secure key stores through a wrap/unwrap signer interface. You can plug signing into your existing key infrastructure; the library never persists raw key material, and keys are zeroed from memory after every signing operation.
- Signer-first accounts: keys never need to live in application code
- Built-in wrap/unwrap pattern for KMS, HSM, and custom secure-store backends
- Safer defaults for both prototype and production workflows
HD wallets, built in
Hierarchical-deterministic (HD) wallets are now part of the standard toolchain in both languages. TypeScript exposes a first-class API through AlgoKit Utils for deriving and managing accounts from a master seed. Python installs xhd-wallet-api automatically as a dependency of AlgoKit Utils, giving developers direct access to the same derivation scheme. Both implementations are BIP-44 compliant and follow ARC-52 for Algorand-specific derivation.
This makes it easier to derive and manage multiple accounts without relying on additional libraries. For teams building consumer wallets, custodial platforms, or other multi-account experiences, this reduces setup and simplifies the integration.
General improvements across the board
In addition to the major changes, this beta includes several improvements:
- ARC-56 is now the default app spec format in both languages, with automatic conversion for existing ARC-32 specs
- One client, purpose-built namespaces for transactions, accounts, apps, assets, and network, same shape in both languages
- Fluent, chainable construction for atomic groups and complex flows, with a one-word switch to simulate
Taken together, these updates make the libraries easier to work with in everyday development.
Getting started
A quick scope note before the install: this release is AlgoKit Utils beta (the TypeScript and Python libraries). It does not include the AlgoKit CLI or anything else under the AlgoKit umbrella. You should also expect breaking changes before the stable release, so please test thoroughly and before using these libraries in production.
To try the beta, clone one of the starter repos and follow the README:
Each repo is a minimal beta-ready starter that already uses the current AlgoKit Utils beta. The README in each repo has the exact setup, build, test, and deploy steps.
We're looking for practical feedback from developers who are actually building with the beta. The best places to send it are:
- GitHub issues for TypeScript and Python
- Algorand Discord, for quick questions and early feedback
If something feels rough, broken, or unclear, this is the right time to report it. That feedback will help shape the stable release.
Resources
- AlgoKit Utils TypeScript docs quickstart, API reference, and core patterns
- AlgoKit Utils TypeScript on GitHub source, releases, and issues
- @algorandfoundation/algokit-utils on npm published versions and dependencies
- TypeScript v9 to v10 migration guide for existing v9 projects
- AlgoKit Utils Python docs, quickstart, API reference, and core patterns
- AlgoKit Utils Python on GitHub source, releases, and issues
- algokit-utils on PyPI published versions and dependencies
- Python v4 to v5 migration guide for existing v4 projects
- Algorand Developer Portal tutorials, starter templates
- Algorand Agent Skills, in-depth skill files for AI coding assistants working with AlgoKit Utils
Happy building
Disclaimer: The content provided in this blog is for informational purposes only. The information is provided by the Algorand Foundation and while we strive to keep the information up-to-date and correct, we make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability, or availability with respect to the blog or the information, products, services, or related graphics contained in the blog for any purpose. The content of this blog is not intended to be legal, financial, or investment advice nor is it an endorsement, guarantee, or investment recommendation. You should not take any action before conducting your own research or consulting with a qualified professional. Any reliance you place on such information is therefore strictly at your own risk. All companies are independent entities solely responsible for their operations, marketing, and compliance with applicable laws and regulations. In no event will Algorand Foundation or any of its affiliates be liable for any loss or damage including without limitation, indirect, or consequential loss or damage, or any loss or damage whatsoever arising from loss of data or profits arising out of, or in connection with, the use of this blog. Through this blog, you may be able to link to other websites which are not under the control of the Algorand Foundation. We have no control over the nature, content, and availability of those sites. The inclusion of any links does not imply a recommendation nor endorse the views expressed therein.