Design & generate

    From schema to production-ready API

    Point API Studio at a database schema or an OpenAPI document and it generates the API spec, the server code, validation, pagination and deployment files — on your desktop or in the cloud.

    How it works

    How API Studio Works

    Comes in

    Database schema
    OpenAPI file
    Existing service

    API Studio

    1. 01

      Connect

      Read tables, fields and relationships from your source.

    2. 02

      Shape

      Rename, filter and map fields; set paging and security.

    3. 03

      Generate

      Produce the spec, service code, tests and deploy files.

    4. 04

      Publish

      Ship to your cloud and gateway with docs attached.

    Goes out

    Live REST API
    Swagger docs
    MCP tools

    Schema-first generation

    Connect to Postgres, MySQL, Oracle, SQL Server or MongoDB and get a clean, paginated REST API.

    Code you can read

    Generated services, data models and tests in the language your team already uses.

    Security baked in

    Authentication, OAuth2/zero-trust adapters, rate limits and secrets are set up before the first deploy.

    Deploy anywhere

    Deploy to AWS, Azure, GCP, Oracle Cloud or Huawei Cloud with infrastructure configs generated for you.

    Also included

    • OpenAPI 3.1 output
    • Swagger version history
    • Field mapping & renaming
    • Gateway publish (cloud or APISIX)

    Inside the product

    How the flow happens in API Studio

    Screens captured from the running platform — no mockups.

    1. Pick a source

      Choose from 30+ databases and warehouses

      Start in the DB → API wizard. Pick from SQL, NoSQL, warehouse, search, vector and graph databases — Postgres, Oracle, SQL Server, MongoDB, Snowflake, Databricks and more — then follow the steps across the top: source, connection, tables, field mapping, API type, security, generate.

      Jundago API Studio wizard showing the database catalog and the seven-stage generation path
    2. Connect safely

      Test the real connection, then reach private data

      Enter credentials or pull them from the encrypted vault, test the live connection, and choose how Jundago reaches private data: IP allowlisting, VPC peering / PrivateLink, SSH bastion or on-premises connectivity.

      Jundago API Studio database configuration step with connection test and private connectivity options
    3. Publish for humans and agents

      Ship the API, then expose it as MCP tools

      Generated services come with an OpenAPI spec, validation, pagination and tests. From the same catalog you add authentication, publish to a gateway, and turn selected operations into MCP tools any AI agent can call with a single partner token.

      Jundago publishing API operations as MCP tools