Ask for a change, then ship it

Project Matrix is the portal where you open a request against the app we built for you, judge the preview, and ship it.

The loop

One request, one preview, one change

Each request is a single thread about a single change to a single app. A Sylo engineer can read every change before you see its preview, and on a Sylo-hosted app one always does.

Request

You describe the change you want in plain language, in one thread under the app it belongs to.

Build

Sylo’s platform turns the request into a change and shows you the stage it has reached.

Preview

A running copy of your app with that change applied, which you judge before anything reaches production.

Ship

You approve the preview and the change goes to production through your app’s hosting choice.

Stages

Five stages, in plain language

These five words are the whole default view. The fuller record of a build is one click away and stays off until you ask for it.

Stage	What it means
Understood	Your request has been read, and what it asks for is written back to you.
Planning	The change is planned against your app as it stands today.
Building	The change is being written.
Checking	Checks run: the review, the tests and the rules every change passes before it can ship.
Preview ready	A running copy carrying your change is up, and it is yours to judge.

Notices reach you by email and in the portal for two events only: preview ready, and review needed.

Hosting choice

Your cloud, or ours

You make this choice once, when the app comes into Matrix, and it decides which terms cover that app. The portal is the same either way: Matrix is how a change is asked for under both ways of working, not a third one.

Own tenant

Production runs in your own cloud account. Matrix ships to it through one scoped deploy role you grant, shown in the portal and yours to revoke.

Your cloud account, in your name
One deploy role, revocable at any time
The repository is yours from the first commit

Sylo-hosted

Production runs in an environment Sylo operates and you never administer. One environment per customer, stated in the portal terms.

Production in us-east-1
Daily backups, kept 30 days
No cloud console. Ask for your own account and we build there instead

See both ways of working

Subscription

A tier, an allowance, a trial

This is the shape a Matrix subscription takes. The prices are not set yet, so none is printed here; what production costs follows your hosting choice and is quoted in your estimate, separately from the tier.

tier

A monthly tier

A tier is one fixed monthly price for the portal and the build allowance inside it.

Upgrade when you need more
Priced from our own costs, never from yours
Portal terms you accept at signup

allowance

An included allowance

Every tier includes a build allowance for the month. When it is spent, builds stop until you upgrade or the month rolls over.

Nothing is metered
No overage and no surprise line
Builds stop rather than keep charging

trial

A trial before the first month

14 days then a paid month

The trial is the real portal, so nothing you can see changes when it converts.

One app, on the smallest tier
Card captured at signup
Cancel inside the 14 days and no month starts

Version 1

What it does not do yet

Written down so nobody discovers it later. Matrix is designed and not open, and the first version draws these lines deliberately.

Subject	In version 1
Apps	Register an app we already host, or start a new one. Moving an app’s hosting in is a Sylo-assisted engagement.
Repositories	A repository Sylo already hosts. Bringing one in from elsewhere arrives with the first customer who needs it.
People	Two roles: an owner who ships, pays and invites, and collaborators who open requests and converse.
Your end customers	They never sign in. They get what your app does, under your brand, with a small Powered by Sylo mark.
Signing in	A magic link, Google or Apple. No passwords.
Country and language	The United States only, in English and Spanish.
Support	Business hours, a reply within one business day, in the portal. No SLA and no credits.

Your request history and your code are used to support and run your app, never to train or tune anything. That sentence is in the portal terms.

Start with the first build

A price and a rough number of increments in 5 working days, before you pay for anything.

Scope a project See pricing