EasyGLM
Fit insurance pricing GLMs, check model performance and export rating tables from a local browser workbench.
Install and open
Requires Python 3.10–3.14. Run in a terminal:
pip install --upgrade easy_glm
easy-glm-workbench
Your browser opens automatically. Keep the terminal open while you work. Restart the workbench after upgrading.
Build a model
- Load data. Open your file or try the French motor claim-frequency or Swedish motorcycle claim-cost example. Supports CSV, Parquet, Excel, Arrow/Feather and SAS files.
- Choose variables. Set the target, exposure/weight and predictors. Check for missing data, possible leakage and redundant predictors before fitting.
- Explore. See observed rates and exposure by variable.
- Fit. Choose a model family, training/holdout split, factor shapes and interactions, then click Fit model.
- Review. Check actual versus expected, lift, Gini and variable importance. Compare alternative models.
- Adjust. Smooth, cap/floor or edit relativities, then apply your changes. The original fit stays available for comparison.
Supports Poisson, Gamma, Tweedie, Gaussian, binomial and inverse Gaussian GLMs, with regularisation and two-stage interactions.
Export and keep your work
| Export | What you get |
|---|---|
| Excel | Applied rating tables |
Scorer (.easyglm) |
Applied rates for scoring new data |
| Project JSON | Model setup, applied adjustments and named snapshots |
| HTML report | Data summaries, importance, coefficient paths, rating factors and diagnostics |
| Python script | Reproduce the model from its source data |
Before closing, save the project JSON and scorer. Reopening a project requires its source data and a refit; fitted runs and session Undo are not saved in project JSON.
Already working in Python?
Open a pandas or Polars dataframe in the workbench:
import easy_glm
easy_glm.launch_workbench(data=df)
Workbench walkthrough · Python examples · Changelog
Why I built this
This started with my wish to port R's aglm to Python and give it a GUI. It's built primarily for my own pricing work and will probably have plenty of bugs, because… vibecode yo. Check the results before using them.
1 maintainer
Release files for easy-glm 0.471
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| easy_glm-0.471.tar.gz | 747.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| easy_glm-0.471-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.3 MB
Release files / easy_glm-0.471.tar.gz
| Download URL | easy_glm-0.471.tar.gz |
|---|---|
| Size | 747.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
683a55e5c39a4e514a4008821a464ac871bde0066372e413d366c535d57f503c
|
|
BLAKE2b-256 checksum How to use checksums |
ea26132a8ececac91847f2707ba475aebf8d605c24e3edadd150c665f5e53c43
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency logRelease files / easy_glm-0.471-py3-none-any.whl
| Download URL | easy_glm-0.471-py3-none-any.whl |
|---|---|
| Size | 542.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ac35462880464f5cfeeb0e82be4d277e86fa2a188598b73ddb663030ed9f4dc0
|
|
BLAKE2b-256 checksum How to use checksums |
7ce29b8d3bbc57704884b78cb5210e025aa343ce7d0526345043f5c374f65239
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency log
