Skip to main content
Craftkite

Languages and frameworks

Build in the language you choose

Web apps, APIs, mobile apps and libraries — planned, written, tested in a real sandbox and published by the same agent, in the framework you name.

Start buildingSee the credit table

Open today

27 frameworks in 11 languages, open today

Each framework here passed Craftkite’s quality checks — real apps built, tested and reviewed — before members could use it. Name one in your request, or let Craftkite choose.

  • TypeScript

    • Next.js

      Web app

    • Expo (React Native)

      Mobile app

    • Hono API (TypeScript)

      APIService

    • Vite + React

      Web appStatic site

    • Nuxt (Vue)

      Web app

    • Angular

      Web app

    • SvelteKit

      Web app

    • TypeScript library

      Library

  • Python

    • FastAPI (Python)

      APIService

    • Django (Python)

      Web app

    • Python package

      Library

  • JavaScript

    • HTML, CSS and jQuery

      Static site

  • C#

    • ASP.NET Core API (C#)

      APIService

    • ASP.NET Core (C#, Razor Pages)

      Web app

  • Java

    • Spring Boot API (Java)

      APIService

    • Spring Boot (Java, Thymeleaf)

      Web app

  • Kotlin

    • Spring Boot API (Kotlin)

      APIService

  • PHP

    • Laravel API (PHP)

      APIService

    • Laravel (PHP)

      Web app

  • Go

    • Go API

      APIService

    • Go web

      Web app

  • Ruby

    • Ruby on Rails

      Web app

    • Ruby gem

      Library

  • Rust

    • Axum API (Rust)

      APIService

    • Rust crate

      Library

  • Dart

    • Flutter

      Mobile app

    • Dart package

      Library

Any other language: choose “Any language” in the studio for universal mode. Craftkite builds on a best-effort basis and tells you what it could and could not check.

Building an API? See what every API gets

What every project gets, in every language

  • Built and tested in a real sandbox

    Craftkite installs the toolchain, runs the build, the tests and the linters, and fixes what fails before you see it.

  • A live preview

    Web apps open in the preview, APIs in the request explorer and command-line tools in a terminal — in the studio and the mobile app.

  • A database when it needs one

    Apps that store data get a database with its migrations, and a data viewer in the studio and the mobile app.

  • Sign-in for your users

    Craftkite Accounts gives apps in any language sign-in with email, social accounts and two-factor authentication, without identity code to write.

  • Publish with one tap

    Each framework goes live its own way — a container, a static site or a store build — chosen for you.

  • Code you own

    Download the project or sync it to your Git host. It runs without Craftkite.

Libraries, released to their registries

Write a library and Craftkite builds, tests and releases each version to its registry under your own account — never under Craftkite’s.

  • TypeScript library → npm
  • Rust crate → crates.io
  • Python package → PyPI
  • Ruby gem → RubyGems
  • Dart package → pub.dev

A release: 50 credits

One request, several parts

Ask for a web app, a mobile app and the API behind them in one request. Craftkite plans the parts, builds them in order with typed clients and publishes them together.

Project memory

Craftkite keeps a short record of each project’s decisions — the framework, the data model, what you asked to keep — so later changes follow them. You can read and edit it.

Honest limits

  • A framework is listed only after it passes the quality checks; new ones are added as they pass.
  • Windows-only frameworks such as the classic .NET Framework are not supported; Craftkite suggests moving to modern .NET.
  • Sandboxes have no graphics cards, so training machine-learning models is out of scope.