Frequently Asked Questions

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.

SolidX is licensed under the Common Public Attribution License 1.0 (CPAL 1.0), an OSI-approved open-source license. See the Terms & Open-Source License page and the license included in the applicable source repository for details.

Yes. Individuals, startups, agencies, and enterprises may use SolidX personally or commercially with no license fees, revenue caps, or production-use limits. CPAL 1.0 attribution, notice, and source-availability conditions still apply.

Yes. CPAL 1.0 permits modification, redistribution, self-hosting, and commercial network deployment. External Deployment is treated as distribution, so covered source, notices, and the required SolidX attribution must remain available as specified by the license.

Where CPAL 1.0 Section 14 applies, graphical interfaces must prominently retain the official SolidX logo, the phrase Powered by SolidX, and https://solidxai.com. Your own branding may appear alongside this modest attribution, but the SolidX attribution may not be removed, hidden, or obscured.

You retain your rights in your metadata, configurations, business logic, and original application code. Pure generated output that contains no CPAL-covered SolidX code is not subject to CPAL merely because SolidX generated it. If generated output incorporates covered SolidX code, those covered portions remain subject to CPAL 1.0, including applicable attribution and source obligations.

No. Enterprise Support is an optional paid service for teams that want SLAs, onboarding, training, architecture guidance, or direct engineering support. It does not grant permission to use SolidX and does not change your CPAL 1.0 rights. See the Enterprise Support page for details.

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.

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.

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 Enterprise Support 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.