Getting started with Niki
Niki is a private AI workspace for teams and is currently in pre-launch preparation. Contact us to discuss current access before planning a rollout for your organisation.
Registration and a paid order are separate
Creating an account does not by itself purchase a paid subscription. A paid order requires a separate checkout and payment confirmation. Review the plan and order details presented there before committing to a purchase.
Registration, billing and deployment flows exist, but their presence does not mean Niki has commercially launched. This site does not promise a free trial, an immediate workspace or a launch date. Ask us which access arrangements are currently available for your team.
Prepare your organisation’s access
Use your own account, provide accurate details and verify your email when requested. If you act for an organisation, you need authority to do so. Workspace administrators manage membership and permissions; billing owners and authorised billing administrators manage subscriptions. The iOS and Android apps are for existing customers: sign in with your existing account and select an authorised workspace. The mobile apps do not offer registration or purchases.
Available features, seats, model allowance and plugin access depend on the selected plan and workspace settings. You need a compatible device, an internet connection and accounts for any services you want to connect. Confirm those requirements before choosing a workflow.
Start with a bounded task
Choose a task whose result you can check: for example, compare three proposals or turn meeting notes into a draft update. State the intended audience, the questions to answer and the output you need. Add only the source files needed for that task.
You can begin with files rather than connecting an entire set of services. Enable a connected tool only when the work needs it. Review the plan, progress and returned output; you can change the instructions or stop the task.
Review before sharing or repeating work
AI-generated results can contain errors. Check factual claims and source material before using the output, especially when it affects customers or business decisions. Drafting an update and sending it are distinct actions; consequential actions require explicit authorisation.
After a workflow is useful, scheduled tasks can repeat authorised work and return results to its conversation. Define the scope and review expectations before scheduling it. Closing the browser does not stop an already scheduled backend workflow.