Live Cloudflare and GitHub connectors, plus verified launch checks

Know what your website
actually is.

Flizent reads the real state of every site you build, straight from the infrastructure. Your clients get a view they can actually understand, and nothing ships half-finished.

Start free See how it works

No credit card required · Clients are free, always

Connects to Cloudflare GitHub Vercel Soon Shopify Soon Webflow Soon Stripe Soon
The difference

Ticket boards guess. Flizent knows.

Jira tells you what someone said they did. Flizent tells you what the website actually is, because it reads the infrastructure itself.

Generic project trackers
Status is whatever someone last typed
Clients can't read a ticket board
Passwords shared over email and chat
The launch checklist is a stale doc
Change developers and the access goes with them
Flizent
Status read from the infrastructure, with the time of reading
A client view written in plain language
Scoped, revocable tokens, never a password
Launch checks verified, or clearly marked unverified
Access belongs to the website, not the person who set it up
Product

Built for the way websites actually get shipped

Each part exists because agencies lose real hours to it: chasing clients for files, re-checking launch steps, hunting for who has access to what.

Infrastructure connectors

Connect Cloudflare and GitHub per website. Zone status, DNS records, real SSL expiry, branches and environments appear on their own, so the board never drifts from the truth.

Launch checks

DNS, SSL, certificate expiry, zone status, ownership, blockers and outstanding content, evaluated from real readings. If we can't verify something, we say so instead of guessing.

Client portal

Your client sees progress, what you need from them and what happens next. Every DNS record, commit and version number is translated out before it reaches them.

Requests, not reminders

Ask for a logo, product photos or provider access in one step. The client gets a clear card, uploads directly and responds in a thread, so nobody has to dig through email for files.

Websites and projects

A website is a long-lived asset. Builds, redesigns, SEO passes and retainers are projects under it, so the history stays with the site through every engagement.

Audit trail

Who invited whom, who connected what, who revoked access, and when. A timestamped record of every change, kept per workspace.

Launch checks

A score that refuses to guess.

Most readiness numbers count unknowns as passes, or as failures. Flizent does neither. Each check is pass, fail or not yet verifiable, and the score only counts what was actually checked.

So "7/7" means seven real readings passed. It never means nobody looked.

novaraskincare.com5/6verified · 1 unverified
DNS records existCloudflare
SSL certificate activeCloudflare
Zone status activeCloudflare
SSL not expiring within 30 daysExpiry not reported
Someone is assignedFlizent
No project is blockedFlizent
All content requests resolved2 open
Read from Cloudflare 4 minutes ago
How it works

Connect once. Stay current.

A few minutes per website. After that, Flizent keeps itself up to date.

01

Add the website

Create the site in your workspace, or accept an invite from a client who already owns it. Either way it appears in your own dashboard.

02

Connect the stack

Add a scoped Cloudflare token or install the GitHub app. Or ask your client to connect it themselves with a guided, no-jargon flow.

03

Share with the client

They see progress, open requests and launch status in plain language. The "any update?" emails stop.

The principle Flizent is built on

The client owns the website.
The developer operates the technology.

Clients approve outcomes in plain language, never technical scopes. Developers get exactly the access the work needs, and it can be revoked at any time.
For clients

You own the website. Not your developer.

Create a free workspace before you've hired anyone. Gather your material, bring in a developer, and keep everything if you ever change who builds it.

01

Start your workspace

Add your website and the people involved. It's free for clients, with no card and no time limit.

02

Get your material ready

Upload your logo, brand colours, copy and photos while you're still deciding who to hire, so whoever you bring in starts with everything in place.

03

Invite a developer

Send an invite by email. They get access to your website only, nothing wider, and you can revoke it whenever you like.

04

Watch it get built

Progress, what's outstanding and whether it's ready to launch, updated automatically and written for a human.

The part nobody tells you

Change developers without losing your website.

Connections and files are stored against your website, not against the person who set them up. If a developer moves on, you revoke their access and the next person picks up where the last one stopped.

This is one of the most common ways small businesses lose control of their own site. It's why Flizent is built this way.

WebsiteYou own it
Provider connectionsYou own them
Brand filesYou own them
Developer accessRevocable
Free for clients. Create your workspace
Security

Access you can explain to a client.

Flizent never asks for a password. Every connection is a scoped token the client can see and revoke.

AES-256-GCM

Encrypted at rest

Provider tokens are encrypted and bound to the website they belong to. They never appear in pages, logs or responses.

Read-only

Least access first

Connectors start read-only. Wider access is a separate, explicit grant from the website's owner.

Per website

Scoped by default

A developer invited to one website sees that website, and nothing else in the workspace.

One click

Revocable anytime

The owner revokes a person or a connection instantly. Access ends on the very next request.

Pricing

Simple pricing. Clients are free.

Priced on websites and team seats only. If you're the client, Flizent is free for you.

Solo

For independent developers running a handful of sites.
$19/month
Start free
  • 3 websites (one per domain)
  • 1 team seat
  • All connectors
  • Client portal
  • 3 months audit history
Most popular

Studio

For small agencies shipping client work continuously.
$79/month
Start free
  • 15 websites (one per domain)
  • 10 team seats
  • Everything in Solo
  • Connector management access
  • 12 months audit history

Enterprise

For larger teams with procurement and security review.
Custom
Contact sales
  • Unlimited websites and seats
  • SAML single sign-on
  • White-label client portal
  • Unlimited audit history
  • Priority onboarding
Building a website for your business?

Client workspaces are free. Invite your developer and keep ownership of everything.

Create a free workspace
FAQ

Common questions

Does Flizent replace Jira, Linear or Slack?
No. Those coordinate work; Flizent tracks the website itself. Most teams keep their tracker for tasks and use Flizent for what's actually true about each site and what the client needs to see.
Do you store my clients' passwords?
Never. Connections use each provider's own permission system: a scoped Cloudflare API token, or the GitHub app installed on chosen repositories. Tokens are encrypted at rest, and the website's owner can revoke them at any time.
Which platforms do you support today?
Cloudflare and GitHub are live. Vercel, Shopify, Webflow, Stripe and Google Analytics are next. We'd rather support the tools web teams use every day in depth than hundreds of them shallowly.
What does "not yet verifiable" mean on a launch check?
It means we couldn't get a real reading, usually because a provider isn't connected yet or didn't report that value. We show it separately rather than counting it as a pass or a failure, so the score only reflects what was actually checked.
Can clients use it without technical knowledge?
Yes, that's the point. Clients see progress, what's needed from them and launch status in plain language. They never see DNS records, commits or deployment logs, and they approve outcomes rather than technical permissions.
A client invited me. Do I need a separate account?
No. Accept the invite with your existing account and the website appears in your own dashboard, marked as owned by your client. You get the full technical workspace; they stay the owner.
Do I need a card to start?
No. Create your workspace, add a website and connect it without entering any payment details. Client workspaces are free, always.

Stop guessing. Start knowing.

Set up your first website in a few minutes.

Start freeTalk to us
Back to Flizent

Privacy Policy

Last updated 18 October 2026
ON THIS PAGE
What we collectWhy we collect itProvider credentialsWho we share withHow long we keep itYour rightsCookiesContact

What we collect

We try to collect as little as possible. In practice that means three categories:

  • Account information — your name, email address, workspace name and the role you hold. Passwords are stored only as a cryptographic hash; we never see the original.
  • Workspace content — the websites, projects, files, requests and activity you create while using Flizent.
  • Technical data — IP address, browser type and timestamps, recorded against actions for the audit trail and for security investigation.

We do not buy data about you from third parties, and we do not build advertising profiles.

Why we collect it

To operate the service you asked us to operate: authenticating you, showing you your own data, sending you service notifications, and keeping a record of who did what for security and dispute resolution. We also use aggregated, non-identifying usage data to understand which parts of the product work and which don't.

Provider credentials

This is the part most people care about, so we'll be specific.

We do not store provider passwords. When you connect GitHub, Cloudflare or another service, you authorise it on that provider's own site and we receive a scoped access token. That token is encrypted at rest, is limited to the permissions the work requires, and can be revoked by you at any time from your workspace without contacting us.

Where a provider offers no such mechanism and an API key must be stored, it is encrypted at rest and never returned to a client-role session. Every use of a credential is recorded in the audit trail.

Who we share with

We share data with the infrastructure providers required to run Flizent — hosting, database, object storage, email delivery and payment processing. Each processes data on our instructions and nothing more. We do not sell personal data, and we have no interest in a business model that would require us to.

We disclose data to authorities only where legally compelled, and where permitted we will tell you first.

How long we keep it

Workspace data is retained while your account is active. If you cancel, your data remains available in read-only form for 90 days so you can export it, and is then deleted. Audit records are retained for the period stated in your plan. Backups roll off within 35 days.

You can request immediate deletion at any time, and we'll action it within 30 days.

Your rights

Depending on where you live, you may have the right to access, correct, export or delete your personal data, and to object to certain processing. We extend these rights to everyone regardless of jurisdiction, because maintaining two standards would be both awkward and dishonest. Email privacy@flizent.com and we'll respond within 30 days.

Cookies

We use cookies that are strictly necessary to keep you signed in and to protect against cross-site request forgery. We do not use advertising or cross-site tracking cookies. Product analytics, where used, are configured not to identify individuals.

Contact

Questions, corrections or complaints: privacy@flizent.com. If you believe we've handled your data badly, tell us before you tell a regulator — we would genuinely rather fix it.

A note on this document: this is our own plain-language policy, written to be readable rather than to sound impressive. It is not a substitute for legal advice, and it should be reviewed by a qualified lawyer in your jurisdiction before you rely on it commercially. If anything here is unclear, email legal@flizent.com and we'll explain it properly.
Back to Flizent

Terms of Service

Last updated 18 October 2026
ON THIS PAGE
The agreementAccounts and workspacesWho owns whatAcceptable useThird-party servicesPaymentAvailabilityLiabilityEnding the agreementChanges

The agreement

By creating a Flizent account you agree to these terms. If you're accepting on behalf of a company, you confirm you're authorised to bind it. If you don't agree, please don't use the service.

Accounts and workspaces

You're responsible for the security of your account and for everything done under it. Keep your password to yourself, enable two-factor authentication where it is available, and tell us promptly if you suspect unauthorised access.

Every workspace has an owner. The owner controls membership, billing and deletion. Members you invite receive only the permissions their role allows, and the owner can revoke that access at any time.

Who owns what

You own your content. Websites, projects, files, credentials and everything else you put into Flizent remain yours. We claim no ownership over it and use it only to provide the service.

We own Flizent. The software, design, brand and documentation are ours. Your subscription grants you a licence to use the service, not to copy or resell it.

Client-owned workspaces stay with the client. Where a client owns the workspace, the credentials, domains and files belong to that client — not to any developer or agency invited into it. This is deliberate and we will not override it on request from an invited party.

Acceptable use

Don't use Flizent to break the law, infringe someone's rights, distribute malware, attack other systems, or store material you have no right to store. Don't attempt to access data belonging to another workspace, probe our systems without written permission, or resell the service as your own.

We may suspend an account that is doing serious harm, and we'll tell you why.

Third-party services

Flizent connects to services we don't control — GitHub, Cloudflare and others. Those providers set their own terms, change their APIs, expire tokens and occasionally go down. We work to minimise the disruption, but we can't guarantee another company's behaviour and we don't accept liability for it.

In particular: we cannot promise that a single authorisation will last forever, because that decision belongs to the provider, not to us.

Payment

Paid plans are billed in advance, monthly or annually. Prices are exclusive of tax unless stated. If a payment fails we'll retry and notify you; if it stays unpaid, the workspace moves to read-only rather than being deleted.

Client-owned workspaces are free and we intend to keep them that way. If that ever changes we'll give at least 60 days' notice, and it will not apply retroactively to existing workspaces.

Availability

We aim for high availability and publish our status openly. We don't currently offer a contractual uptime guarantee on self-serve plans; enterprise agreements can include one. Planned maintenance is announced in advance where possible.

Liability

Flizent is provided as-is. To the extent the law allows, our total liability in any twelve-month period is limited to what you paid us in that period. We're not liable for indirect or consequential loss, including lost profits or lost data where you had a reasonable means of export.

Nothing here limits liability for fraud, death or personal injury caused by negligence, or anything else that can't lawfully be limited.

Ending the agreement

You can cancel at any time from the billing page. We may terminate for serious or repeated breach, with notice and an opportunity to fix it where the situation allows. On termination your data stays available in read-only form for 90 days before deletion.

Changes

We may update these terms. For material changes we'll give at least 30 days' notice by email and show the date at the top of this page. Continuing to use Flizent after that means you accept the revised terms.

A note on this document: this is our own plain-language policy, written to be readable rather than to sound impressive. It is not a substitute for legal advice, and it should be reviewed by a qualified lawyer in your jurisdiction before you rely on it commercially. If anything here is unclear, email legal@flizent.com and we'll explain it properly.
Back to Flizent

Refund Policy

Last updated 18 October 2026

If Flizent isn't right for you, we'll refund you.

No forms, no retention call, no asking you to justify it. Email us within 30 days of a charge and we'll process it.

The 30-day guarantee

Any paid plan can be refunded in full within 30 days of the charge. This applies to your first payment and to any renewal you didn't expect. Email billing@flizent.com from the address on the account and we'll process it within five business days, back to the original payment method.

You don't need to explain yourself. We'd appreciate a sentence about what didn't work — it's genuinely how we improve — but it isn't a condition.

Annual plans

Cancel an annual plan mid-term and we'll refund the unused whole months on a pro-rata basis. We won't keep money for a service you've stopped using.

Renewals you didn't mean to make

We email a reminder before every annual renewal and before a trial converts. If one slips past you anyway, tell us — we'll refund it. We don't consider revenue from a subscription somebody forgot about to be revenue worth keeping.

What we can't refund

To be straight with you, there are limits:

  • Charges older than 30 days, other than the pro-rata annual case above.
  • Fees charged by third parties — domain registrars, hosting providers, payment processors — that we never received.
  • Accounts terminated for serious breach of the terms.

Free plans and client workspaces

Client-owned workspaces are free, so there's nothing to refund. You can delete a workspace whenever you like and export your data first.

What happens to your data

A refund doesn't wipe your account immediately. Your workspace moves to read-only and your data stays available for 90 days, so you can export everything at your own pace. Nothing is deleted without warning.

Ask us anything

Billing questions, disputes, or a situation this page doesn't cover: billing@flizent.com. A person reads it, and we'd rather resolve something fairly than argue about a clause.

A note on this document: this is our own plain-language policy, written to be readable rather than to sound impressive. It is not a substitute for legal advice, and it should be reviewed by a qualified lawyer in your jurisdiction before you rely on it commercially. If anything here is unclear, email legal@flizent.com and we'll explain it properly.