---
title: "Project Status"
description: "Current package status, API stability, and release expectations for RoomSharp."
canonical: "https://roomsharp.dev/docs/v0.5.4/preview-notice"
source: "src/content/v0.5.4/preview-notice.mdx"
---
# Project Status
RoomSharp packages are available on NuGet and can be used in real projects. The project is still pre-1.0, which means the public API may continue to evolve as the ecosystem is finalized.
---
## Current Status
RoomSharp is fully functional from a runtime and generated-code perspective. The NuGet packages are public, documented, and designed for real applications.
The current `0.5.x` line focuses on stabilization, provider compatibility, generated-code consistency, CLI polish, and long-term maintainability after the Smart Entity Lifecycle work introduced in `v0.5.0`.
The source code repository is not yet publicly available. That is the main meaning of the current pre-1.0 project status.
---
## API Stability
RoomSharp is still under active development.
The core concepts and architecture are stable: source-generated DAOs, explicit SQL ownership, provider-aware runtime behavior, migrations, and attribute-driven models.
Before the first stable `1.0` release, public APIs may still receive targeted refinements. Breaking changes are documented in release notes, and migration guidance is provided where possible.
For how package versions are coordinated across the ecosystem, see the [Release Model](/docs/v0.5.4/release-model).
---
## What's Available Now
- **NuGet Packages:** Published packages for the core runtime, providers, extensions, CLI, and integrations.
- **Source Generator:** Compile-time DAO and database implementation generation.
- **CLI Tool:** Scaffolding, migrations, inspection, query execution, and project configuration commands.
- **Documentation:** Guides for core APIs, QueryExtensions, dependency injection, CLI, lifecycle features, and release history.
- **Benchmarks:** Performance metrics and comparisons with Dapper.
- **Multi-Provider Support:** SQLite, SQL Server, PostgreSQL, MySQL, and MariaDB.
---
## Official NuGet Packages
| Package | Description |
|---------|-------------|
| [RoomSharp](https://www.nuget.org/packages/RoomSharp) | Core package with SQLite support |
| [RoomSharp.SqlServer](https://www.nuget.org/packages/RoomSharp.SqlServer) | SQL Server provider |
| [RoomSharp.PostgreSql](https://www.nuget.org/packages/RoomSharp.PostgreSql) | PostgreSQL provider |
| [RoomSharp.MySql](https://www.nuget.org/packages/RoomSharp.MySql) | MySQL/MariaDB provider |
| [RoomSharp.DependencyInjection](https://www.nuget.org/packages/RoomSharp.DependencyInjection) | DI extensions |
| [RoomSharp.QueryExtensions](https://www.nuget.org/packages/RoomSharp.QueryExtensions) | Dapper-like raw SQL API |
| [RoomSharp.Reactive](https://www.nuget.org/packages/RoomSharp.Reactive) | Reactive queries, computed views, caching, and UI binding helpers |
| [RoomSharp.Reactive.WinForms](https://www.nuget.org/packages/RoomSharp.Reactive.WinForms) | WinForms binding helpers for `BindingList`, `BindingSource`, and `DataGridView` |
| [RoomSharp.Cli](https://www.nuget.org/packages/RoomSharp.Cli) | CLI tool for scaffolding & migrations |
---
## What's Coming Later
As the ecosystem moves toward a stable `1.0` release:
- **Open Source Repository:** Full source code on GitHub.
- **Public Issue Tracking:** GitHub Issues for reports and feature requests.
- **Community Contributions:** Pull requests and extension packages.
- **Extended Samples:** More example projects and templates.
---
## Can I Use RoomSharp in Production?
Yes. The packages are stable enough for real projects when you are comfortable using a pre-1.0 library and following release notes for API refinements.
Recommended production approach:
- Keep RoomSharp ecosystem packages on matching versions when possible.
- Pin package versions in production applications.
- Review the [Changelog](/docs/v0.5.4/changelog) before updating.
- Use generated DAOs for core data access paths and QueryExtensions for ad-hoc or reporting queries.
---
## Design Philosophy
RoomSharp deliberately avoids feature creep.
New capabilities are added only when they align with its explicit, predictable design philosophy:
- **Compile-time code generation** instead of runtime reflection
- **Explicit, predictable behavior** over magic
- **Multi-provider support** with provider-specific optimizations
- **Performance-first** with zero-allocation hot paths
---
## Staying Updated
To stay informed about RoomSharp's progress:
- Watch the [NuGet package](https://www.nuget.org/packages/RoomSharp) for updates
- Check this documentation site regularly
- Follow the [Roadmap](/docs/v0.5.4/roadmap) for planned features
- Read the [Changelog](/docs/v0.5.4/changelog) for version details
---
## License
MIT