Running eze as a service, No Code App Development

eze Agency Implementation, Building Internal Tools for Enterprise Clients

Learn how to position eze as a productized service for enterprise clients needing internal tools without custom development. This course covers deploying static sites with built-in databases, configuring company sign-in access control, and automating tool generation through AI agents to compress project timelines from weeks to days.

Open the decision record for eze

What does running eze for clients commit you to?

Published figures for this service. Blank fields are not published.

Monthly tool cost
eze is open-source under the MIT license, no vendor license fee is published. Costs to model: your infrastructure (server, domain, TLS) and identity provider seats, plus delivery labor.
Time to first value
Not published
Payback
Not modeled, requires client price, labor hours, infrastructure and identity provider costs, and expected volume, none of which are supplied
Guided implementation
8 hours

Is eze worth running as a client service?

The evidence supports a viable niche service: self-hosted private internal tooling for clients that already run SSO and have a server, with a built-in backend and AI-agent deployment via MCP. It does not support public-facing sites, managed SaaS delivery or white-label resale, and delivery economics remain unmodeled until your agency supplies cost and price inputs.

An agency-fit judgement for reselling this service. It is separate from the tool description on the decision record.

Before you start

What has to be in place before the first client engagement.

Tools and subscriptions

  • Server with a domain, wildcard DNS and HTTPS
  • Company identity provider: Google Workspace, Okta, Entra ID or an OpenID Connect provider
  • eze CLI for `eze deploy` and `eze init`
  • AI coding agent connection via eze mcp (Claude Code, Cursor or other MCP apps)
  • Access to Claude or OpenAI models for eze.ai features

People and inputs

  • Agency operator with server, DNS and HTTPS provisioning skills
  • Identity provider admin rights to register eze with the client's SSO
  • A static HTML/CSS/JS codebase to deploy as the first site
  • Documented runbook for eze.db, eze.files, eze.ws and eze.id usage

Included with the course

7 working documents for delivering this service.

  • eze Project Scoping Worksheet for Internal Toolsworksheet
  • Company Sign-In Configuration Checklist (Google Workspace, Okta, Entra ID)checklist
  • eze Deployment SOP: From AI Agent to Live Sitesop
  • Internal Tool Pricing Template (Database Tiers, File Storage, User Seats)template
  • eze.mcp Integration Guide for Claude Code and Cursor Workflowsguide
  • Real-Time Collaboration Feature Setup (Rooms, Live Updates, Permissions)checklist
  • Self-Hosted Infrastructure Requirements and VM Sizing Guideguide

Listed by name. These documents are not yet published as individual downloads.