NNative Platform

Secure workspace

Opening NativeCMS…

Checking your session and loading the right workspace.

Please wait

Loading your dashboard…

NNative Platform

Invite-only limited beta

Build an approved, low-risk Drupal site with NativeCMS.

This beta is for selected UK business testers. Applications are reviewed first and do not create an account; approved applicants receive a separate, email-bound activation code.

Welcome back

Sign in to your workspace

Invite-only beta

Accept the beta documents for this workspace

How workspaces work

Keep the right people and sites together

A workspace is the shared home for one business, client or project. It has its own sites, team, activity and plan limits.

Everyone in a workspace can see its sites. Their role controls what they can do: Owners and Administrators manage the team and settings; Release Managers can deploy to Production; Developers work in Development and Testing; Viewers can look but not change anything.

Members cannot see your other workspaces. Create a separate workspace when a client or project needs its own team, sites or plan.

Beta check-in

How are you getting on?

A short note every so often helps us improve NativeCMS while it is in beta.

Please do not include passwords, access keys, customer records or other sensitive information. Feedback is linked to your account and workspace and handled under our Privacy Policy.

New workspace

Create a separate workspace

Use a separate workspace for a client or project that needs its own sites, team and plan. It starts on the Free sandbox plan and can be managed independently.

New site

Create a Drupal site

1 of 2 · Site

You can edit this address before creating the site. Native adds the Development, Testing and Production prefixes automatically.

Your approved private review site only

Native installs the supported Drupal release for the site purpose we approved. Development, Testing and Production stay private throughout this review programme. Public access and customer domains are not included.

Team access

Team members

Invite someone by email. They can sign in or create a Native account before accepting.

Release

Accept release

After code is released

Git conflicts are never auto-resolved. Resolve them in your branch before accepting a commit, so every environment receives the exact reviewed release.

Code moves through this release flow. Database and uploaded files stay in this environment; use Database & Files to make a separately recorded content copy.

Release recovery

Restore the previous release

This changes the deployed code only. The environment's database and uploaded files are not restored, and database updates are not reversed.

Restore environment

Confirm restore

Current code, database and uploaded files in this environment will be replaced. Other environments are not changed.

Release details

Deployment log

Loading…

Security check

Confirm it is you

For sensitive changes, confirm your password. If authenticator-app security is enabled, enter its current six-digit code too.

Keep your account safe

Save your recovery key

Store this key in a password manager. It is the only self-service way to reset your password, and Native cannot show it again.