Build your website with AI.
Run it as your own CMS.

Download SpaceBuilder
Build and maintain this site with AI
Build a website for an architecture studio. Group projects into residential and hospitality, with individual pages for photos and design details, and a project inquiry form.
  1. Tell the AI which pages and data fields you need.
  2. Review and edit the pages and API permissions.
  3. Upload the project files, create a release and activate it.
  4. After launch, check advisories and updates, then repeat AI-assisted review and testing.

A company site. A member service.
Built on Webspace.

Company and brand websites

Company news, product information and a customer file area.

Similar serviceWordPress

Member resources and communities

Member files and conversations, with access by team and level.

Similar serviceDiscourse

Product information and order intake

Product pages and order or booking intake on your database and APIs.

Similar serviceWooCommerce

Payments, shipping, settlement and POS need separate integration.

Platform names are for comparison only; no compatibility or migration is implied.

One SpaceBuilder,
10,000 concurrent connections.

A Go server that passed authenticated WebSocket and REST API load tests.

Realtime WebSocket

Concurrent authenticated connections
10,000
Events delivered
100,000 / 100,000

REST API, with 10,000 connections held

Read requests
10,000
Write requests
1,000
Test conditions and results

Measured on October 27, 2026 on a single Go server. Ten events were sent to each of 10,000 authenticated WebSockets in three runs; each run received all 100,000, with nothing missing or duplicated. The same connections were held for 67 seconds through twelve rounds and received all 1,200,000 deliveries, and delivery still passed after 100 connections were dropped and reconnected. The DB read and write check was measured on SQLite3: with the connections held, 1,000 writes and 10,000 reads finished in 3.11 seconds with no HTTP 429 and no write errors. SQLite handles writes one at a time per database, so PostgreSQL, which locks per row, suits write-heavy workloads better. Connections are held by the Go server, so connection count and database throughput are separate figures; 10,000 is the tested scale, not a maximum. PostgreSQL throughput is measured separately. Conditions: loopback load generators on the same machine, raised request limits, no TLS, proxy or external network; the count is sockets of one account.

Test environment and per-run data

Your website and workspace.
The same members and files.

The site your visitors use and the space your team manages share members, permissions, files and APIs.

Webspace

The website customers and members visit

Members · Permissions · Files · APIs

Workspace

The place your team manages files and work

Explore the built-in features
  • Sign-up and sign-in
  • Teams and levels
  • Permissions and admin
  • Chat
  • Uploads and downloads
  • File server
  • WebSockets
  • Schema API

Tools for building, publishing and running your site.

Manage data, APIs, access and operational metrics in one place.

Keep updating and reviewing security after launch.

When new vulnerabilities (CVEs) are disclosed or code changes, the operator reviews the changes with AI assistance and checks them with actual tests.

  1. Check security advisories and dependency vulnerabilities
  2. Apply server and library security patches
  3. Review changed code and its impact with AI
  4. Retest access permissions and core functions
View data, API and release settings
View requests, API traffic and error logs
  • Request and error trend

    Requests, server errors and refused connections over 24 hours or 7 days.

  • Traffic by DB and API

    Call counts and response speed for each API, by database.

  • Error log

    Records failed requests with status code, target and response time.

  • Connections and runtime

    The WebSocket dispatch queue with the DB pool, storage and average latency.

PlannedAI monitoring is planned for a future release.

Member, login and web security settings
Permission and testing examples

Create the interface with AI.
Review security before going live.

Services that handle members and files need access rules and verification. Connect existing features and define security requirements for your business.

A customer-only page

Review example

Built-in features to use

Registration, login, teams, levels and file access permissions

Security requirements to review

  • Access scopes for customers, staff and administrators
  • Login attempt limits and session expiry
  • Rules for changing or revoking access

Scenarios to test

  • Can one customer open another customer’s file URL?
  • Does access stop after logout or permission revocation?

Verification continues after security setup.

  1. Design and code review
  2. Automated security checks
  3. Attack and misuse testing
  4. Fixes and retesting

Alongside automated checks, use test accounts and data to check access bypasses, invalid input and concurrent requests. Keep applying security updates and retesting after launch.

OWASP security testing guidance
Server setup and additional integrations

Built into Webspace

Connect existing features to your service.

  • Members, teams, permissions and files
  • Schema APIs and live connections
  • Site deployment and release switching
  • Login, CORS and CSP settings

Environment and verification

Prepare these for your service.

  • Domain and TLS certificates
  • Backup and restore checks
  • Updates and dependency reviews
  • Permission, integration and regression tests

Separate development

Add specialist features as needed.

  • Payments, refunds, shipping and settlement
  • POS hardware and external systems
  • Data migration from an existing site
  • Business rules and additional screens

Start building the site you have in mind.