# Feature availability and limits

Check the public contract of a ParticleDB release before choosing a client, runtime or migration strategy.

Source: https://particledb.ai/reference/limits/

## Verify the installed release

```bash
particledb --version
particledb start --help
```

Record the server and client versions together. Examples checked against one release do not automatically establish the behavior of an older one.

## Distribution and version

The installation instructions use the standard downloadable server. Core query, Redis and Python Particle examples were checked with `1.1.19-rc.16`.

| Capability | Standard `1.1.19-rc.16` binary |
|---|---|
| SQL clients, HTTP SQL and Redis clients | Included; use their separate connection addresses |
| Native client listener | Enabled by default on the database port, 7173; see [connection addresses](/installation/ports/) |
| Python Particles | Included in the free edition; needs Python 3.11 or newer with the `particledb` package on the server host; see [Particles](/particles/overview/#availability-and-requirements) |
| Transactional schema changes | Enabled by default on supported single-node transaction modes; see [schema changes](/sql/transactional-ddl/) |
| Historical reads | Opt-in with `--enable-time-travel`; separate from backup and recovery |

## Important boundaries

| Area | What to verify |
|---|---|
| Connections | The address for the selected client; not all interfaces share one listener |
| Transactions | Isolation, conflicts, schema commands and connection ownership |
| Data movement | Supported formats, server-side paths and export scope |
| Particles | Python version, dependencies, privileges and loading method |
| Agent workflows | Built-in execution versus application-managed worker patterns |
| Compatibility | Catalog queries, migration tools, extensions and lock semantics |
| Operations | Backup and restore commands included in your edition |

## SQL compatibility

An accepted connection or a parsed SQL statement is not proof that every behavior of another database is implemented. Test the exact operation, returned values and failure cases your application depends on.

## Resource limits

Memory, connection and execution limits depend on the configured server. See [memory](/operations/memory/), [connections](/operations/connections/) and [Particle limits](/particles/limits/).

## Unsupported behavior

Treat a feature-not-supported error as a boundary to handle or redesign around. Do not remove safeguards or depend on silently ignored options to make a migration succeed.

## Related

[Documentation home](/docs/) · [Troubleshooting](/guides/troubleshooting/)