← Horizech LabsHorizech Workspace

The CMS/ERP
that bends
to your needs.

Providers define the interfaces. Plugins implement them. Apps use them. Compose the system your team actually needs — then run it on our infrastructure or your own.

Open Workspace →Talk to us

Composition

The interface is ours. The implementation is your choice.

A provider is the contract your code writes against. A plugin satisfies it. Change your mind about mail, storage or payments and you swap the plugin — the apps above never notice.

Database
PostgreSQL
Email
SESSMTP
Media
BunnyDatabaseFile
Logger
ConsoleDatabaseFile
Payment Gateway
StripeRevenueCat
Authentication
Identity
Authorization
Access Manager
External Auth
Google
OAuth2
OAuthLink
Object Storage
Bunny
Key Store
Database
Cache
In Memory
Background Jobs
Hangfire
Encryption
AESRSA
Hash
SHA512
Archive
Zip
Internationalization
i18n
Branding
BrandWizard

18 providers, 24 implementations. Install as few as you like.

Apps

What your team actually opens.

Each one is a package in its own right. Install the three you need and leave the rest out — an unused app is not sitting in your instance being a liability.

Collections StudioPortalMedia LibraryRecordsBlogsCoursesTasksNotesProfileAuditSitemapImport ExportWorkspace ManagerHourglassText-to-SpeechCaptain Password →

Provisioning

From one click to a running instance.

Creating a workspace starts a five-step pipeline. Each step waits on the one before it, and you watch it happen — including which step failed, if one does.

  1. A database of its own
    A dedicated Postgres database and role are created for the instance. Nothing is shared with anyone else’s workspace.
    postgres · dedicated role
  2. Credentials into the vault
    Those credentials go into OpenBao rather than a config file. The instance reads them at boot with its own token, and re-provisioning revokes the old one.
    secret/workspaces/<id>/database
  3. The service goes up
    It deploys to the region you picked, sized from the CPU and memory your plan grants, with a persistent volume attached.
    HWS_INSTANCE_CPU · MEMORY_MB
  4. A domain pointing at it
    A workspace subdomain is issued and wired up. Plans that allow it can attach your own domain instead.
    ws-xxxx.horizech.cloud
  5. Limits written down
    Your plan’s entitlements are copied onto the instance as a snapshot. If a plan changes later, what you already run does not move.
    STORAGE_GB · CUSTOM_DOMAIN_ALLOWED

Where it runs

Our infrastructure, or yours.

The same platform either way. The difference is who runs the database and who gets paged.

Managed

We provision it, run the database, hold the secrets and keep it updated. You get a working instance and a dashboard to watch it come up.

  • Postgres handled for you
  • Secrets kept out of your config
  • Pick the region at creation
  • Attach your own domain, plan permitting
Open Workspace →
Self-hosted

Skip the pipeline entirely. You get an instance token and an access code, then run the launcher wherever you like — your hardware, your network, your rules.

  • Runs on Docker, anywhere you can
  • Same packages and entitlements
  • No inbound access needed from us
  • Your database stays yours
Ask about self-hosting