Skip to main content
Floorkit is a browser-based TypeScript SDK for building design applications. Your app owns its interface and storage. Floorkit supplies the building model, geometry, editing, and drawings. Start with the quickstart, then choose a workflow below. Each path uses the public package and the same saved building data.

AI floor-plan apps

Turn an agent’s proposed JSON into a design that people can edit.

Browser CAD

Add building authoring to your own Three.js scene.

Architecture and BIM tools

Make plans, sections, and scaled drawing sheets from one building.

Property and space planning

Edit a floor plan, label supplied room outlines, and read their areas.

​
AI floor-plan generation

Input: a user request and building JSON proposed by your AI model. Result: a checked building model, editable geometry, and a saved project file.
  1. Define the model contract with Building model and Coordinates and units.
  2. Follow the agent building workflow to check unknown JSON and return errors for correction.
  3. Open the project and mount a plan editor or 3D editor.
  4. Let the agent propose supported commands and let the person review the result. Keep the same project and undo history.
  5. Save and reopen the design. Add sheets when you need a PDF.
Floorkit does not supply the AI model or produce a plan from a text prompt by itself. Your app handles inference and design requirements. Model validation and geometry checks do not certify building-code compliance.

​
Browser CAD

Input: your scene, camera, renderer, and typed building data. Result: building elements in your scene, with supported 2D and 3D edits.
  1. Use your Three.js scene. Await kernel initialization before creating geometry.
  2. Use ProjectManager for one project with building data, views, sheets, and history. Use BuildingSession when your app owns the project structure separately.
  3. Mount a plan editor and connect a 3D editor to that same project.
  4. Use edit commands for saved changes. Your own Three.js objects can remain in your scene.
  5. Dispose the editors and project when the view closes. Your app disposes its own renderer and controls.
You supply the toolbar, storage, and application workflow. For general solid modelling without building elements, consider the OpenGeometry kernel.

​
Architecture and BIM tools

For early site feasibility, follow the Site massing playbook to compare building footprints, heights, floor area and supplied zoning controls before modelling walls and rooms. Input: storeys, building elements, saved view definitions, and a sheet layout. Result: plans, straight sections, exterior elevations, and PDF drawing sheets.
  1. Start a building, add walls, doors, and storeys.
  2. Create a plan view, then cut a section or create an elevation.
  3. Compose a sheet with scales, dimensions, notes, and a title block.
  4. Export a PDF or GLB model.
  5. Save the JSON project too. A PDF or GLB is not an editable Floorkit project.
IFC and DXF exports are coming in the next release. Use the currently available outputs when your app needs to ship now. Sections use straight cuts; other drawing limits are in Views and sheets. Floorkit supplies geometry and drawings, not structural or MEP certification.

​
Property apps and space planning

Input: a building model and room outlines supplied by your app or user. Result: an editable property plan, room labels and areas, and a design that can be reopened.
  1. Create a project with a plan view.
  2. Add a plan editor so people can move walls, doors, and windows.
  3. Define a room with its name, number, and outline. Read its area in square metres.
  4. Keep the room outline current when the design changes. Floorkit does not detect rooms automatically from walls.
  5. Save the project, then compose a sheet and export a PDF when the user asks.
Your app decides what an area means for its property or planning workflow. Check measurements and drawings against that workflow before sharing them as official records.

​
Try the workflows

The live examples show modelling, editing, saving, and drawing exports. Each guide with a live frame links to its corresponding example. For a coding agent, start with Build with agents. For a new developer, start with the quickstart. Local development is free; any deployed hostname needs a valid license key. See Licensing.
Last modified on October 14, 2026