[data-reveal]{opacity:1!important;transform:none!important}
AntelopeJS DMS
Back to the overview

Use case You already have a product

You already have the software?Get the back office in minutes.

Your ERP, your time clock, your accounting: each keeps its data in its own database. Connect them to the DMS as they are, SQL or NoSQL. The AI maps their schemas into one back office the same day, as code you own, and soon answers your team's questions across all of it. Want to try it first? The connect demo template runs the DMS on a sample PostgreSQL, MongoDB or RethinkDB database, in Docker. Then start your own project from the starter template and connect your database.

npx @antelopejs/core project init dms-connect-demo --template dms-connect-demo
  • PostgreSQL · MongoDB · RethinkDB
  • Your app untouched

01 How it works

From connection string to back office.

  1. 01 Connect

    Name a connection

    The URL stays in an environment variable. We recommend a read-only role.

  2. 02 Map

    The AI reads the schema

    Tables, fields and relations from the catalog. Never a row, never a secret column.

  3. 03 Review

    You validate the plan

    Pages, dashboards and the code behind them. Nothing runs before you press Run.

  4. 04 Use

    Your team gets to work

    Search, edit where you allowed it, and follow your numbers on dashboards.

02 Supported today

The databases you already run.

  • PostgreSQL

    Tables, foreign keys and enums mapped into pages, filters and relations.

  • MongoDB

    Collections and their document shapes, inferred from the catalog and aggregates.

  • RethinkDB

    Tables and indexes mapped into pages and dashboards over the data you already have.

03 Then, in production

Your team asks. The AI does the rest.

Next for the AI module: support, sales and ops ask in plain words, schedule prompts and plug in their agents, right in the dashboard they already use.

operator · NODE_ENV=production Coming soon
  • As the user, never more. It sees and does what the connected user can, minus a global exclude list you control.

  • Scheduled prompts. Weekly reports and nightly checks that run with their creator's permissions.

  • Every action is logged. Attributed to the user it ran for.