DEV.co
Open-Source ERP · steedos

steedos-platform

Steedos Platform is an open-source, low-code enterprise application builder that uses metadata-driven architecture and AI to generate business software. It aims to replace manual coding and drag-and-drop with text-to-app capabilities powered by ObjectStack (ObjectQL, ObjectOS, Object UI).

Source: GitHub — github.com/steedos/steedos-platform
1.6k
GitHub stars
413
Forks
TypeScript
Primary language
AGPL-3.0
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repositorysteedos/steedos-platform
Ownersteedos
Primary languageTypeScript
LicenseAGPL-3.0 — OSI-approved
Stars1.6k
Forks413
Open issues578
Latest releasev2.7.32 (2026-02-04)
Last updated2026-07-06
Sourcehttps://github.com/steedos/steedos-platform

What steedos-platform is

TypeScript-based platform implementing metadata-driven architecture with ObjectQL (schema protocol), ObjectOS (headless runtime), and Object UI (React/Tailwind renderer). Supports multiple databases (MongoDB, PostgreSQL), auto-generates GraphQL/REST APIs, and provides YAML-based workflow automation and RBAC.

Quickstart

Get the steedos-platform source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/steedos/steedos-platform.gitcd steedos-platform# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Rapid Enterprise Application Development

Build CRM, ERP, and BPM applications in days rather than months by defining business logic via metadata and AI prompts instead of writing boilerplate code.

Database-Agnostic SaaS Platforms

Deploy the same metadata-driven application to multiple database backends (MongoDB, PostgreSQL, JSON) without code changes, enabling flexible infrastructure choices.

Organizations Scaling AI-Generated Code

Teams exploring AI-native development workflows where ObjectQL metadata serves as the standard interface between AI models and deployed applications.

Implementation considerations

  • AGPL-3.0 license requires source code disclosure if modifications are distributed; confirm your deployment model (internal vs. SaaS) aligns with copyleft obligations.
  • Platform is mid-migration from monolithic Steedos v2.x to modular ObjectStack architecture; evaluate stability risk and plan for eventual upgrade path.
  • ObjectQL metadata format and ObjectOS API surface appear central but concrete spec documentation and examples availability require direct review of /docs.
  • Require in-house TypeScript/Node expertise for custom component development and operational support; community-driven maintenance may have response time variability.
  • Database choice (MongoDB vs. PostgreSQL vs. JSON) must be decided early; unclear if runtime database switching is supported post-deployment.

When to avoid it — and what to weigh

  • Proprietary Closed-Vendor Lock-In Preference — If your org requires vendor support SLAs, commercial licensing guarantees, or closed-source infrastructure, AGPL-3.0 and community-driven governance may not fit.
  • Mission-Critical Production Systems Without Internal DevOps — Steedos is actively transitioning to ObjectStack architecture; v2.x is supported but future focus is on the new modular stack, requiring in-house maintenance capability.
  • Legacy System Integration at Scale — No clear data provided on pre-built connectors to SAP, Oracle, or other legacy enterprise systems. Custom integration development likely required.
  • Real-Time Collaborative Editing Requirement — Platform positioning centers on schema-driven generation and automation; concurrent multi-user editing patterns are not prominently documented.

License & commercial use

Licensed under AGPL-3.0 (GNU Affero General Public License v3.0). This is a strong copyleft license: modifications to the software, if distributed or delivered as a service (SaaS), require publishing source code under the same license. Internal use without distribution may avoid disclosure, but any external deployment (cloud, customer-facing) triggers source code obligations.

AGPL-3.0 permits commercial use but imposes strict conditions: if you deploy Steedos as a SaaS offering or distribute modified versions, you must publish all modifications under AGPL-3.0. Internal enterprise use without external distribution faces no license restrictions. **Recommend legal review before committing to commercial SaaS deployment.** No clear commercial support, SLA, or indemnification terms provided.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationAdequate
License clarityClear
Deployment complexityModerate
DEV.co fitGood
Assessment confidenceHigh
Security considerations

Platform advertises built-in RBAC down to field level and enterprise security; specifics (encryption at rest/transit, audit logging, vulnerability disclosure process, authentication protocols) not provided. AGPL-3.0 means source code is publicly visible, easing security review but also exposing implementation details. No mention of penetration testing, bug bounty, or certified security audits. Self-hosted deployments inherit infrastructure security responsibility.

Alternatives to consider

Salesforce (Proprietary)

Market-leading metadata-driven platform with extensive pre-built apps, commercial support, and AI (Einstein). Trade-offs: proprietary, cloud-only, expensive, vendor lock-in.

Budibase (Open Source, MIT License)

Open-source low-code platform with simpler metadata model and easier commercial licensing. Trade-offs: smaller ecosystem, less AI integration, narrower enterprise feature set.

OutSystems (Proprietary)

Mature low-code platform with strong DevOps integration and commercial support. Trade-offs: proprietary, vendor lock-in, higher TCO, less AI-native.

Software development agency

Build on steedos-platform with DEV.co software developers

Steedos offers compelling AI-native and metadata-driven architecture but requires careful assessment of AGPL-3.0 obligations, architectural transition risk, and in-house support capability. Devco can help audit licensing, design deployment architecture, and guide pilot implementation.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Related on DEV.co

Explore the category and the services that help you build with it.

steedos-platform FAQ

Can I use Steedos for a commercial SaaS product?
AGPL-3.0 permits commercial use, but if you run Steedos as a service (SaaS), you must publish your source code and any modifications under AGPL-3.0. Internal enterprise use without external distribution avoids this. Legal review strongly recommended.
What databases does Steedos support?
MongoDB, PostgreSQL, and JSON-file storage are mentioned as supported. Database is abstracted via ObjectQL metadata, but runtime switching or multi-database deployments require documentation review.
Is Steedos production-ready?
v2.7.32 is actively maintained, but the project is mid-migration to ObjectStack architecture. Evaluate stability tolerance; community-driven support means no SLA. Strongly consider pilot projects and in-house DevOps capability.
How much coding do I need to do?
Core intent is text-to-app via AI and metadata; however, custom business logic often requires TypeScript function definitions and component customization. Estimate 20–40% custom code for non-trivial enterprise apps.

Software developers & web developers for hire

Adopting steedos-platform is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate open-source erp software in production.

Evaluate Steedos for Your Enterprise App Strategy

Steedos offers compelling AI-native and metadata-driven architecture but requires careful assessment of AGPL-3.0 obligations, architectural transition risk, and in-house support capability. Devco can help audit licensing, design deployment architecture, and guide pilot implementation.