Battery simulation, structured for engineers and agents
Built by the creators of PyBaMM
Battery development is slow because the path from test data to simulation results is manual and specialist-dependent. Ionworks structures that entire workflow so it runs repeatably — so teams cover more ground with fewer bottlenecks.
Trusted by
Ionworks took an open-ended problem and helped us to quickly identify the best course of action, delivering a tailored model of our system.
Ionworks enables our R&D Services customers with tools and insight that support faster development and more predictable outcomes.
Ionworks gives our customers the tools to reduce their development time and cost to implement Iontra Charge Control protocols in their products.
Built by the team behind PyBaMM
Ionworks was founded by the creators and maintainers of PyBaMM, the open-source battery modeling package used across academic and industrial R&D.
Ionworks Studio brings that electrochemical depth into a web platform where engineers and agents operate the same interface — accessible through the REST API and Python SDK.
The problem with battery simulation today
Battery R&D teams need software that understands the structure of battery data, models, and experimental protocols. Not a generic simulation platform that promises speed and optimization in the abstract.
The challenge
Scattered cycling data
Results live across shared drives, email, and vendor-specific file formats. Nobody is sure which file is current or which cycler produced it.
What Ionworks does
One system of record
Every measurement is normalized, linked to its cell spec and experimental context, and searchable. Ionworks reads Maccor, Neware, Novonix, Arbin, BioLogic, and BasyTec natively. The data layer stands alone or feeds parameterization and simulation.
The challenge
Parameterization bottlenecks
A DFN or SPMe model is only as useful as its parameters. Connecting data to model, fitting, and validating is manual and error-prone.
What Ionworks does
Parameterized models
A model, a validated parameter set, and a cell spec combined into one reusable object. The unit of work that makes simulations reproducible.
The challenge
Slow build-test-iterate cycles
A fast-charge study can tie up cycler channels for weeks. Simulation answers the same question in minutes.
What Ionworks does
Protocol-driven simulations
Charge at 1C to 4.2V, rest 10 minutes, discharge at C/3. Simulation accepts the protocol formats your team already uses — saved, typed, or uploaded from a cycler file.
The challenge
PyBaMM does not operationalize itself
Running a simulation in a notebook is straightforward. Turning it into a repeatable, traceable workflow across a mixed-skill team is a different problem entirely.
What Ionworks does
Reproducibility and coordination
When a colleague runs the same parameterized model against the same protocol, the result matches. Immutable models and simulation reuse remove the guesswork about inputs.
How Ionworks works
01
Measure
Your team's single source of truth for battery test data. Ingest files from all major cyclers — Maccor, Neware, Novonix, Arbin, BioLogic, BasyTec — into a normalized, searchable system. Every measurement stays linked to its cell, its protocol, and its experimental context. Teams that need structured data management without simulation use this layer on its own.
02
Train
Fit physics-based models to your experimental data. Select a model type, define the parameters to estimate, and generate a parameterized model your team can trust across studies.
03
Predict
Run protocol simulations against parameterized models before committing cycler time. Evaluate fast-charge strategies, assess lithium plating risk, or compare internal states across cell designs.
04
Optimize
Define engineering targets and search for the best design or protocol. Vary electrode thickness, porosity, loading, or charging strategy while managing degradation and plating constraints.
Built for your code, not just your browser
Everything in Ionworks Studio is available through the REST API and Python SDK. The same programmatic surface is what makes Ionworks work for AI agents — an automated system operates the platform through the same interface a human engineer uses. No separate "AI mode." The API was there first.
Who we work with
Every battery team hits the same wall eventually: physical testing can’t keep up with the questions their programs need answered. Simulation closes the gap, and looks different depending on the product.
Automotive OEM
Catch battery risk before tooling locks
Challenge
Cell issues found in physical validation arrive after supplier contracts and production timelines have locked around the wrong assumptions.
Ionworks in action
Cycler data feeds parameterized models for each candidate cell. Duty-cycle simulations run in parallel with the test plan, so design questions get answered in days.
Outcomes
Engineering decisions move earlier. Late-stage redesigns drop. Programs hit their gates.
Drone & Advanced Air Mobility
Push past the bench-tested envelope
Challenge
Real missions cover thermal, altitude, and load conditions no lab campaign can reproduce. Datasheets stop being useful at the boundaries.
Ionworks in action
Validated physics models extrapolate where data ends. Trade studies sweep range, safety, and lifetime against mission profiles in an afternoon, not a year of cycler time.
Outcomes
More usable flight time per cell. Defensible operating limits. Faster iteration on the airframe-pack interface.
Materials Development
Connect new chemistry to system impact
Challenge
A promising coin-cell result rarely survives the jump to a real product. Translating material gains into pack-level value takes months.
Ionworks in action
Each new dataset slots into a parameterized model. The impact of a coating change or electrolyte tweak on energy, lifetime, and safety shows up in hours.
Outcomes
Faster down-selection between candidate chemistries. Quantified value for partners. Fewer prototype builds before commercial conversations.
Consumer Electronics
De-risk launches without slowing them
Challenge
Battery surprises tend to surface near the end of a product cycle, when the cost of change is highest and the launch window is fixed.
Ionworks in action
One system of record tracks every cell variant, charging profile, and aging assumption. Models predict behavior under realistic usage instead of waiting for survey data.
Outcomes
Predictable performance at launch. Smaller late-cycle scope changes. More design freedom for the product team.
Frequently asked questions
Start with your workflow
If your team is spending more time rebuilding simulations than running them, Ionworks Studio can help. Bring your data, your models, and your protocols.