Database-first / Existing-database-first

From existing databases to generated, reviewable handoff.

DegoDB turns existing databases or schema designs into canonical metadata, PHP-focused generated artifacts, API surfaces, no-code Web previews, and verifiable handoff materials.

Start locally See support scope

Source Database Schema Existing DB / designed schema

Core Canonical Metadata Reviewable source of truth

Generated DataClass / DBAccess

Surface OpenAPI / HTML / no-code

Handoff Source Output / Bundle

What DegoDB does

It turns database structure into reviewable development artifacts.

DegoDB connects schema import, canonical metadata, generated artifacts, API surfaces, and verification materials. The public site only states capabilities backed by the current implementation and samples.

Metadata

Schema import

Import database schemas into canonical metadata used as the basis for generated output.

PHP output

DataClass / DBAccess

Generate PHP-focused DataClass and DB Access layers, verified through samples and contract gates.

API surface

OpenAPI / proxy runtime

Generate API surfaces and PHP-focused runtime artifacts from database-backed metadata.

Handoff

Source Output / bundle

Keep generated artifacts, project metadata bundles, and AI/developer handoff context reviewable.

No-code on database metadata

The no-code layer sits on the database-first foundation.

DegoDB no-code Web previews are not a standalone visual builder with a hidden data model. They are generated from canonical metadata and reviewed Source Output artifacts.

Generated screens list / detail / form

Artifact NO-CODE-RUNTIME

Delivery publish candidate approval

Preview URLs current / alias

Live data read-only runtime-data.json

Submit boundary managed-operation sync outbox

UI evidence metadata / DOM / browser smoke

Use cases

Explore, generate, and hand off from an existing database.

Existing DB exploration

Import an existing schema and inspect its metadata and generated artifacts.

Database-first development

Keep schema, DataClass, DBAccess, API surfaces, and documentation aligned.

No-code preview

Generate list/detail/form previews from reviewed metadata and inspect approved preview URLs.

Implementation handoff

Package metadata bundles, generated artifacts, and verification results for review.

Supported scope

Support is described by layer.

MySQL / MariaDB Default mainline for the Mtool config store and generated-output workflows.

SQLite Lightweight config store profile and representative user DB contract coverage.

PostgreSQL Complete for the required opt-in user DB / generated-output lane. Config-store support is intentionally not required.

Firebird Verified for the agreed opt-in Mtool/profile and one-way migration-path scope; not broad Firebird production support.

Output language Current generated output is PHP-focused.

No-code Web runtime preview on database metadata, not a hidden-schema builder.

Proof / Samples

Claims are tied to samples and verification.

Generated artifacts

DATACLASS-PHP, DBACCESS-PHP, OPENAPI-JSON, and PROJECT-METADATA-BUNDLE are tracked as current / verified artifacts.

No-code proofs

sample27-32 cover app-local persistence, generated no-code runtime, sync, domain repetition, and UI contract testing.

Tutorial lane

This overview covers sample01-47, from generated foundations through bounded shared-state/static-first demos. See Mtool documentation for source documents and Samples for playable works.

YouTube guide

Video viewers should land on the same evidence.

DegoDB guide videos use the same support boundaries as this site. The first guide topic is "What Is DegoDB?", introducing DegoDB as a path from existing schema to metadata, outputs, API surfaces, and verification.

Episode 00 What Is DegoDB? Concept and workflow No-code guide Runtime preview boundary Metadata / Source Output / approval Boundary What it is, and is not DB support, output language, no-code scope Samples Samples and proof Back to verified coverage

Quickstart

Run the local stack and one tutorial sample first.

Before deeper design reading, verify the local stack, metadata sync, and the smallest tutorial gate.

make env
make up-mtool
make mtool-canonical-sync
make sample01-pack-runtime-test

Consulting / Implementation support

Align the DB, deliverables, and boundaries before work starts.

Support work should decide schema-only intake, synthetic data, secret sidecar separation, and review scope first. Legal, tax, billing, and compliance readiness are not automatic DegoDB claims.