Websites, portals and dashboards that know your records.

Most websites sit apart from the system behind them, so content gets copied across and goes stale. On Qik, public sites, member areas, customer portals and internal dashboards for your team all read and write the same records as everything else, with sign-in already built.

No credit card. Qikbot is included.

Why it's different

Not a website plugged into a database. One system with a front door.

Website builders make pages. Anything involving your actual people, bookings or members needs plugins and a sync. A Qik site is simply another way into the records you already run on.

Most toolsQik

Content

Typed into the site, or copied over by a plugin on a schedule.

Pages read the live records. Change an event in the dashboard and the site has already changed.

Member sign-in

A membership plugin with its own list of users to keep in step.

Built in. The accounts belong to the same people as your records, under your name on your domain, with Google and Apple sign-in. Your members never see Qik.

Private information

The page hides what a visitor shouldn't see.

The server only sends what that visitor is allowed to have. The same permissions as the dashboard apply, so hidden data never reaches their browser.

Making changes

Brief a developer and wait.

Describe the change to Qikbot, review it in a private draft, then publish. Write your own components when the design calls for it.

Beyond the public site

A separate tool, or a custom build, for every member area, portal and internal dashboard.

The same builder makes them all: a members' area, a portal for families or clients, and dashboards for your team with live counts, lists and forms. Each one has its own sign-in and the permissions you already set.

How it works

01

Describe it

Tell Qikbot what the site, portal or dashboard is for. It builds the pages on your records while you watch.

02

Review the draft

Changes sit in a private draft with its own preview link until you're happy with them.

03

Publish to your domain

Go live on your own domain, with the security certificate issued and attached for you.

Built on Qik

You're looking at one.

This site was designed, built and published on Qik, with the same builder, the same draft-and-publish and the same records you'd use. Nothing here needed a separate website tool.

If it's good enough to sell the platform, it's ready for your site, portal or dashboard.

The basics, covered

Sites, portals and dashboards that are part of the system, not beside it

Everything a site, portal or dashboard needs is already built in.

Live records, not copies

Pages show your real events, people and articles. Change the record and the site changes with it.

Sign-in already built

Accounts, invitations, password resets and Google or Apple sign-in, on your own domain and in your own name.

Member areas and portals

A members' area, or a portal for families, clients or volunteers. Signed-in visitors see their own records and nothing else, under the same permissions as everywhere else.

Your own domain, found by search

Connect a domain and the certificate is handled for you, with titles, share images and a sitemap for every page.

Draft, then publish

Edit safely in a draft. The live site doesn't change until you publish.

Blogs and listings

News, resources and directories that fill from your records, with a page for each item.

Internal dashboards

Screens for your team with live counts, lists and forms on your own records, signed in and limited to what each person may see.

Your own design and code

Start from ready-made blocks, or write custom components when the design calls for it.

Forms on any page

Registrations and payments sit inside your site and write straight to your records.

Personalised apps

One app that changes with whoever is using it

What a visitor can see, what a member can do and what a moderator can manage are settings, not code. Build the app once and every person gets their own version of it, enforced on the server.

  1. 01
    Anyone visitingWhat the app itself is allowed
    Browse public events and newsNo member names or discussions
  2. 02
    Signed inEveryone who joins, through an access pass
    Read the members' board and post commentsSee their own profile and bookings
  3. 03
    Their own recordsOwnership
    Edit or delete their own commentsNot anyone else's
  4. 04
    Their roleA position in a group, like moderator
    Edit or remove anyone's comments in their groupOnly in that group

Each layer adds to the one before. Data a person can't have is never sent to their browser, so the same rules hold in your app, the dashboard, the API and Qikbot. Whatever your use case, the logic for who can do what is already built.

Check it on every screen before it goes live

Switch the draft between desktop and phone sizes in the editor, menu included, then publish when it looks right.

Start today

The hard parts are already done.

Start a free trial and tell Qikbot what you need, or talk to the people who build it. Either way you begin with something that works.

No credit card. Your data stays yours, and you can export it any time.