One calm place for everything about a website.
Connections, launch checks, the client portal, requests and a full history, built around one rule: the owner stays in control while someone else does the work.
Read the infrastructure, not someone’s summary.
Connect Cloudflare and GitHub per website. Flizent reads zone status, DNS records, the real SSL expiry date, repositories and environments, and keeps the reading fresh.
- Cloudflare: zone, DNS records and certificate details through a scoped, read-only token
- GitHub: installed as an app on the repositories you choose
- Several connectors per website, each shown with when it was last read
- Owners can connect accounts themselves through a guided flow
| Type | Name | Content | Proxy |
|---|---|---|---|
| A | novaraskincare.com | 76.76.21.21 | Proxied |
| CNAME | www | cname.vercel-dns.com | Proxied |
| MX | novaraskincare.com | mx1.mailhost.com | DNS only |
| TXT | _dmarc | v=DMARC1; p=quarantine | DNS only |
Ready to launch, with proof.
Infrastructure checks come from the latest connector reading. Project checks come from Flizent itself. Anything we cannot verify is shown as unverified, never guessed.
- DNS records, SSL status, certificate expiry and zone status
- Someone assigned, no blocked projects, no open content requests
- Lists show a plain “5/7”, so nobody mistakes a guess for a measurement
A view your client actually understands.
Progress, what you need from them and what happens next, in plain sentences. Technical details are translated on our servers before anything reaches the client, so nothing confusing or sensitive leaks into their view.
- “Website is live” instead of a zone status
- Requests with direct uploads and threaded replies
- Free for clients, always
Every change, recorded and explained.
Invites, connections, requests and project changes appear in one feed for each website. The audit log keeps the full record: who did what, to which website, and when.
- Plain-language feed for owners
- Timestamped audit log for the team
- History stays with the website, not the person
Built for the way websites get shipped.
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.
Requests and files
Ask for a logo, product photos or account access in one step. The client uploads directly and replies in a thread.
Team and invites
Invite people to the whole workspace or to a single website. Access is granted per website and accepted by the invitee.
Client-owned websites
When a client invites your agency, their website appears in your own dashboard, labelled “Owned by” the client.
Workspaces
Agencies, freelancers and owners each get their own workspace. Switch only when you really belong to more than one business.
Audit trail
Every invite, connection, revocation and change, timestamped and kept per workspace.
The right view for each person.
Permissions are checked on our servers for every request, not hidden in the interface. A developer given one website sees that website and nothing else.
| Role | What they can do |
|---|---|
| Owner | Invite and remove anyone, connect and disconnect accounts, see everything, close the workspace. |
| Developer | Full technical workspace on the websites they are given: projects, connectors, launch checks, files. |
| Client | The plain-language portal: progress, requests, uploads and updates. No technical detail. |
What Flizent is
A control room for websites. The owner keeps the accounts. Agencies and freelancers get narrow, approved access. Flizent watches the infrastructure, records every change and explains it in plain English.
What Flizent is not
Not a website builder, a password manager, a chat app or an AI model. We connect to all of those. We are the neutral layer in the middle, and we never compete with the tools you already use.
See it on your own websites.
Tell us about your websites and we will set up your workspace.
Free for one website · Clients are always free