AutoCore Overview
Understand AutoCore's deployment model, application surfaces, release-candidate status, and documentation starting points.
AutoCore is a configurable vehicle marketplace platform for a separately operated installation. It provides a public marketplace, an Admin application, a versioned API, and a background Worker. PostgreSQL, Redis, and Meilisearch provide the core state, queue/cache, and search services.
Release candidate and external configuration
AutoCore documentation currently describes 1.0.0-rc.1, a Release Candidate. A stable 1.0.0 release is not claimed
here. Commercial installation artifacts, domains, TLS, email/SMS, storage, legal content, payment-provider activation,
monitoring, backups, and operational access remain configuration or delivery boundaries for the operator.
What AutoCore is for
AutoCore is designed for organizations that need to operate a branded vehicle marketplace in one primary market per installation. It separates product behavior from market configuration so an installation can be configured for a country, region, city, locale, currency, timezone, distance unit, and enabled vehicle capabilities.
The current Commercial 1.0 boundary is one primary market per installation. That is an installation model, not a claim that the platform is permanently restricted to one city or country.
Key capabilities
- Public vehicle discovery, listing detail, seller/dealer presentation, and search.
- Admin workflows for marketplace management, catalog data, listings, media, users, and operational controls.
- A versioned API used by the Web and Admin applications and intended to support a future mobile client.
- Worker-backed asynchronous processing for queues such as search indexing, media, notifications, and scheduled marketplace jobs.
- PostgreSQL persistence through Prisma, Redis-backed queue/cache infrastructure, and Meilisearch indexing.
- Edition-aware branding and configuration from one shared platform source.
What an installation contains
| Surface | Responsibility |
|---|---|
| Web | Public marketplace experience and buyer/seller-facing flows. |
| Admin | Authenticated marketplace and operational administration. |
| API | Versioned business API and the server-side application boundary. |
| Worker | Background jobs that should not block interactive requests. |
| PostgreSQL | Durable relational state. |
| Redis | Queue, cache, and short-lived coordination state. |
| Meilisearch | Search projection and query-time filtering. |
| Reverse proxy | Public routing, TLS termination, and service exposure boundary. |
What AutoCore does not provide automatically
AutoCore does not automatically create a commercial relationship, configure a production domain, issue a certificate, activate a payment provider, write jurisdiction-specific legal policies, provide production credentials, or guarantee an operator's hosting, support, compliance, or service-level arrangements. Those responsibilities must be verified and configured for each installation.
Where to go next
- Read Product Status for the RC boundary and verification language.
- Use the Documentation Map to choose a role-specific path.
- Learn the Installation concept before planning setup.
- Review Application Surfaces for the system boundary.