FAQ
Frequently Asked Questions
Everything developers, architects, and technology leaders ask when evaluating SolidX - from how it compares to coding agents to licensing, security, and getting started.
Why SolidXLicensing & PricingTechnical & ArchitectureSecurity, Compliance & OwnershipGetting Started & Adoption
Why SolidX
How SolidX compares to coding agents, traditional frameworks, and low-code platforms.
SolidX is not an alternative to coding agents - it is the framework they generate into. Claude Code, Codex, and Cursor are great at writing code, but they do not standardize architecture, enforce repeatable patterns, or guarantee maintainability on their own. SolidX gives those tools a structured, metadata-driven framework with enterprise patterns already in place, so the output is consistent, reviewable, and production-oriented instead of open-ended. In short: coding agents decide how code gets written; SolidX decides what structure it gets written into.
No. SolidX is AI-native and complementary. It ships with an MCP server that plugs directly into tools like Claude Code, Codex, and Cursor, so your team keeps using the subscriptions and workflows they already have. You get agent productivity and SolidX's enterprise structure at the same time.
Spring Boot and .NET are excellent, but they are lower-level starting points that force teams to rebuild the same enterprise plumbing repeatedly: auth, roles, CRUD, relations, workflows, APIs, admin screens, and validation. SolidX sits at a higher abstraction layer. Common enterprise structure is already in place, metadata drives more of the stack, and recurring patterns are solved once instead of reinvented per project - without giving up code ownership or familiar engineering workflows.
Low-code and no-code tools are strong for quickly assembling internal dashboards, but they often trade away code ownership, flexibility, and engineering-workflow compatibility. SolidX is a framework, not a black box. It generates real, inspectable NestJS + React code that lives in your repo, fits your Git and CI/CD workflows, and can be customized deeply - making it a better fit for strategic, long-lived, or complex enterprise applications.
No. Scaffolding gives you a one-time starting point. SolidX uses metadata as an ongoing source of truth that drives both backend and frontend behavior, standardizes recurring enterprise patterns, supports modular full-stack development, and is designed to work with AI-driven generation over time - not just on day one.
They probably could - the real question is whether they should. Building and maintaining a metadata engine, admin framework, auth layer, and generation workflow is a significant, ongoing investment. SolidX gives you that standardized foundation immediately so your engineers spend their time on business-specific logic instead of rebuilding platform capabilities.
Licensing & Pricing
How the Business Source License works and who owns the generated code.
SolidX is licensed under the Business Source License 1.1 (BSL 1.1). The source code is publicly available on GitHub. Qualifying users can use it free of charge, while larger organizations need a commercial Enterprise License. See the Terms of Service for full details.
Individuals and organizations with less than $1,000,000 USD in total annual revenue (including any funding) can use SolidX free of charge for any purpose, including commercial production use.
If your organization's total annual revenue (including funding) is $1M USD or more, you must obtain a commercial Enterprise License before using SolidX in production. You can contact our team for a tailored proposal, including discounts for non-profits and educational institutions.
You do. All code generated by the platform belongs to the user, with no runtime dependency on SolidX. The generated output can be freely modified, deployed, and distributed. Code built from your metadata and configurations is your intellectual property.
If your agency or freelancing business generates less than $1M annually, you can use SolidX for free, including for client projects. The generated code belongs to whoever deploys it. Organizations above the threshold need an Enterprise License.
No. Because generated code is fully yours and has no runtime dependency on the platform, your applications keep running regardless of your licensing status. The BSL model keeps SolidX sustainable while remaining open and accessible to the community.
Technical & Architecture
The stack, architecture, data modeling, and AI workflow behind SolidX.
SolidX is built on a TypeScript base stack - React on the frontend and NestJS / Node.js on the backend. It is based on open standards, with source published to GitHub and libraries on NPM.
Every application starts from enterprise-ready patterns: skinny controllers, a service layer, a repository layer, interfaces, and dependency injection. This gives you clear separation of concerns, modular services, and inspectable, maintainable code by default - reducing architectural drift across teams and projects.
SolidX is database-agnostic. Support is tested for MySQL, MSSQL, and PostgreSQL, with MongoDB coming soon.
You define your domain model in metadata first, and that metadata drives both backend and frontend behavior. Define entities once and generate APIs, validations, admin UI behavior, and relationships from the same source of truth. UI widgets are chosen by field type, and APIs, validations, and relations stay aligned automatically - giving you speed and consistency without duplicated effort.
SolidX ships an MCP server that works inside tools like Claude Code, Codex, and Cursor, enabling prompt-driven creation of modules, models, APIs, and UI. The agent respects manual developer changes and builds on top of them rather than overwriting your work.
Everything is modular. You can create multiple microservices, and each microservice can contain one or more modules. Each microservice is full-stack - it gets both a set of APIs and an admin UI. APIs are automatically documented with OpenAPI, and you can generate consumer-facing interfaces in addition to back-office admin screens.
Standard field types are supported, including numeric, text, rich text, relation, and media/file fields. Relationships include many-to-one, many-to-many, and one-to-many, with UI behavior adapting automatically based on field metadata.
Security, Compliance & Ownership
Self-hosting, data control, access management, and vendor lock-in.
Yes. SolidX is self-hostable and open. Generated code lives in your environment, can be pushed to your own Git repository, and deployed through your standard CI/CD pipeline - containers, bare metal, GitHub Actions, AWS CodePipeline, ECS, Kubernetes, and more.
No. SolidX is a self-hosted platform and does not transmit your data to Logicloop Ventures Limited. Your data stays entirely on your own infrastructure. We do not collect, store, or sell personal data through the platform.
SolidX includes IAM capabilities: username/password, passwordless OTP via email or SMS, and OAuth providers such as Google, Meta, LinkedIn, and X, with Keycloak support coming soon. Authorization is handled through role-based access control (RBAC), with per-role permissions, record rules that control which data is visible, and API key support.
SolidX is designed for teams that care about control. Generated code is visible, editable, and owned by you, with no runtime dependency on the platform. It fits your Git branching model and deployment tooling, so you get acceleration without surrendering ownership or portability.
Reducing the review burden of open-ended AI code is a core reason SolidX exists. By shaping generation with metadata, architectural conventions, and enterprise scaffolding, the output is repeatable, readable, and aligned with best practices - making it easier to review, maintain, and scale than free-form generated code. It complements, rather than replaces, your own engineering standards and code review.
Getting Started & Adoption
Trying SolidX, fitting your team, and where to go next.
Start with the documentation for setup instructions, prerequisites, and tutorials. The source is on GitHub, and you can join the community on Discord.
SolidX is a strong fit for teams that build internal or external enterprise applications repeatedly, want speed without sacrificing code quality, need inspectable and self-hostable output, and are already experimenting with AI coding tools but want more control and consistency. That includes engineering teams building business systems, platform teams standardizing internal app development, and SI / implementation teams shipping enterprise workflows.
Yes. SolidX is not a replacement for strong engineering standards - it operationalizes them consistently and faster. It generates real code that fits Git, CI/CD, containers, and cloud pipelines, so teams with high standards spend less time re-implementing them across applications.
SolidX Cloud is coming soon. In the meantime, you can self-host SolidX on any infrastructure. Reach out via the pricing page to learn more.
The fastest way to understand SolidX is to see one workflow end-to-end - from metadata and AI prompting to generated APIs, UI, and editable code. Request a demo and our team will walk you through it.
Still have questions?
See SolidX end-to-end - from metadata and AI prompting to generated APIs, UI, and editable code.