No stored cloud keys
LineXa keeps no key to your Google Cloud project. It acts through a dedicated service account with short-lived credentials, which you can revoke at any time.
LineXa deploys into your cloud, not ours. We designed the platform so that it holds as little of your access and data as possible, and so that you can see and revoke what it does.
Many deployment tools ask you to upload a cloud key. LineXa doesn't store one. It acts through a dedicated service account using short-lived credentials, limited to the role you install in your own project.
LineXa keeps no key to your Google Cloud project. It acts through a dedicated service account with short-lived credentials, which you can revoke at any time.
You grant a LineXa role whose permissions are published in plain text, so your security team can review exactly what LineXa can do.
Every workspace has its own database, and DEV, STAGE and PROD are kept apart, each tied to its own Google Cloud project.
All traffic uses HTTPS with HSTS, and the studio is served with a strict Content Security Policy and hardened security headers.
Passwords are stored only as salted bcrypt hashes, and sign-in attempts are rate-limited to slow down guessing.
Deployed environments are health-checked every few minutes. Problems open an incident for the LineXa team, and platform status is public.
LINEXA CONSULTING is registered in France and handles personal data under the GDPR. New projects deploy to an EU region unless you choose otherwise, and the resources LineXa creates stay in your own cloud account.
Send us your questionnaire or ask about a specific control. We answer in plain language.