Support OpenStaad

An unofficial, community-driven project. Your support keeps it free, independent, and actively maintained.

Donate on Ko-fi

Help cover server costs and fuel late-night coding sessions.

Support on Ko-fi

Star on GitHub

Boosts visibility and helps new users discover the project — completely free.

Star on GitHub

Professional Services

Need custom scripts, team training, or a specific feature prioritized?

Development Roadmap

Where the project is headed. Items marked under evaluation are being studied, not promised.

  1. v1.0

    Library Functions

    Core OpenSTAAD functions implemented and published as a Python package on PyPI.

  2. v1.1

    Documentation Site

    First version of the documentation site live with function references.

  3. Feb 2026

    Full API Coverage

    Every function of the OpenSTAAD API is wrapped — 730 functions across geometry, loads, properties, supports, design, analysis, output and view.

  4. Jul 2026

    Complete Documentation

    All implemented functions documented and grouped into searchable domain pages, with a base-units guide and a migration guide.

  5. In progress

    Error Handling & Custom Functions

    A single ops.connect() session, arguments validated up front instead of failing silently, and high-level helpers for common workflows.

  6. In progress

    Published Usage Tests

    A usage test per function — a runnable snippet executed against STAAD.Pro — published on its doc page, so you can see the model it builds, the values it returns and the units it returns them in, plus the STAAD.Pro versions it was verified on.

  7. In progress

    AI-Ready Library

    Make the library easy for AI assistants to use correctly. Live now: /llms.txt, /llms-full.txt and a plain-markdown twin of every doc page. Next: full type hints and docstrings in the library, so Claude, Copilot or Cursor write working openstaad code on the first try.

  8. Under evaluation

    MCP Server

    Studying a Model Context Protocol server that would let an AI agent search these docs and drive STAAD.Pro through openstaad directly. Feasibility, safety around model-modifying calls and whether it belongs in the library are still open questions — not a commitment yet.