Kuika Gate
Security

Secure from the first screen.

Every Kuika Gate app starts with sign-in, roles and its own database. Kuika Gate checks the code before it leaves you, and you decide where the app runs.

In short

Kuika Gate builds apps with security in place from the start: every app has its own database, built-in sign-in, role-based permissions and automatic security scanning. Secrets are stored encrypted and never enter the chat. Companies can host their apps on Kuika Cloud or on their own servers.

Built in

Security that comes with every app.

Every app keeps its own data

Every app gets its own database. While you build, the preview runs in your browser with your sample data, and the test environment has a separate database too.

  • One database per app
  • Sample data kept apart from live data
  • Automatic and named backups you can restore

Sign-in and roles in your apps

Sign-in is not code the AI writes freely; the platform builds it. You choose which role can read, add, change, delete or export which data, and the server enforces the rule, not only the screens.

  • Email verification, password reset and two-step sign-in
  • Permissions per table, screen and action
  • Preview the app as any role or signed out

Enterprise sign-in (SSO)

Your team can sign in to Kuika Gate with company accounts. The web apps you build can use enterprise sign-in too, and directory groups can map to app roles.

  • Enterprise sign-in for Kuika Gate itself
  • OIDC, SAML and LDAP / Active Directory for your web apps
  • Map company groups to app roles

Security scan before publishing

Kuika Gate scans the app after every build: keys written into code, risky code patterns and packages with known vulnerabilities. A deeper AI review is one click away, and every finding points to a real file and line.

  • Critical code findings stop the export to GitHub until they are fixed or closed with a reason
  • When you publish, you see how many critical findings are still open
  • Fix one finding or all of them with AI; Kuika Gate rescans to confirm

Keys stay out of chat and code

API keys are stored encrypted on the Secrets page and never shown again after you save them. When the app needs a key, Kuika Gate asks for it in a secure card, not in the chat.

  • Stored encrypted, write-only
  • Keys never pass through the chat
  • The scan catches keys written into code

Exportable audit log

Important actions in your organization are logged, and you can export the log. Inside every app there is also an activity view that shows who changed which account, role or rule.

  • Organization-wide exportable audit log
  • Password policy, account lockout and session management
  • Account and role history per app

Approved packages only

Apps use packages from a curated catalog. Your workspace can limit apps to approved packages, require approval for new ones and add its own private package sources.

  • Limit packages and require approval
  • Download a software bill of materials (SBOM)
  • License report for every app

Choose where the app runs

Run your apps on Kuika Cloud, where Kuika runs the hosting for you, or on your own servers. You can always download the code; the code is yours.

  • Managed hosting on Kuika Cloud
  • On your own servers, in your own network
  • Download the full source code
FAQ

Frequently asked questions

Can't find your answer? Talk to our team.

Is Kuika Gate secure enough for company apps?

Kuika Gate was made with company use in mind: apps come with sign-in, role-based permissions enforced on the server, security scanning and encrypted keys. Companies add enterprise sign-in (SSO), an audit log and hosting on Kuika Cloud or their own servers.

Where is my app's data kept?

Every app has its own database. While you build, the preview runs in your browser with your sample data. Published apps run on Kuika Cloud or, for companies, on their own servers.

Does the security scan block publishing?

Critical code findings stop your code from being exported to GitHub until you fix them or close them with a reason. Publishing is not blocked, but Kuika Gate tells you how many critical findings are still open.

How are API keys and passwords protected?

They are entered on the Secrets page; values are encrypted and never shown again. When the app needs a key, Kuika Gate asks for it in a secure card, so the key never passes through the chat.

Can we sign in with our company accounts?

Yes. Your team can sign in to Kuika Gate with company accounts; the web apps you build can use OIDC, SAML or LDAP / Active Directory, and company groups can map to app roles.

Do you have security certifications?

We do not list certifications on this site. If your company is running a security assessment, send us your questionnaire and we will answer it in detail.

Have a security questionnaire?

Send it to us. We will answer it and walk your security team through how Kuika Gate works.