Deployment
We run it. You build.
Strive Cloud handles the hosting, security and upgrades, so your team goes straight to building apps.
Contact SalesArchitecture
Built on Google Cloud. Run by us.
Every organization gets its own workspace, its data kept apart and encrypted end to end, on infrastructure we run for you.
- Your team
Secure sign-in
Single sign-on with Google, Microsoft, Okta or any SAML or OIDC provider, and roles for who can do what.
- Your workspace
Yours alone
Your own address, with your data kept apart from every other organization and encrypted on every hop.
- The platform
Run by us
The servers, the scaling and the upgrades are ours to handle. You sign in and build.
- Google Cloud
The foundation
Strive Cloud runs on Google Cloud.
Run it yourself
Need it inside your own cloud?
Strive also runs on Kubernetes in your own AWS, Google Cloud or Oracle Cloud account, or on your own hardware. The same product, on your infrastructure.
Security
Security your IT team will sign off on.
SOC 2 Type II audited controls, encryption everywhere, single sign-on and role-based access. Your data never trains a model.
Security
SOC 2 Type II
Independently audited security controls, tested over time.
Europe
GDPR
Personal data handled under the EU's data protection rules.
California
CCPA
Personal data handled under California's privacy law.
Controls
Encryption
Encryption runs on every layer, built on Google Cloud's security controls. Data is encrypted at rest with keys held in Google Cloud KMS, and every connection is encrypted in transit, including traffic between our own services. The credentials your connections use are encrypted too, and never appear in an app.
- At rest
- AES-256, on Google Cloud.
- Keys
- Held and managed in Google Cloud KMS.
- In transit
- TLS on every connection into the platform.
- Inside the platform
- Traffic between our own services is encrypted too.
- Connection credentials
- Stored encrypted and entered through secure forms. Never shown in apps.
- Exported apps
- Credentials are left out.
No training on your data
Your data is never used to train AI models, and the AI services we use don’t train on it either: we use them on enterprise terms that exclude training. A data processing addendum makes our commitment contractual, and you decide how long your data is kept.
- AI model training
- Your data is never used to train AI models.
- AI services
- Used on enterprise terms, so they don’t train on your data either.
- In writing
- A data processing addendum makes it a contractual commitment.
- Retention
- You decide how long your data is kept.
Single sign-on
People sign in with the identity provider you already use: Google, Microsoft, Okta, or any provider that supports SAML or OpenID Connect. Their groups map to roles in Strive, so the right access follows them in. Systems connect with API keys.
- Providers
- Google, Microsoft, Okta, and any provider that supports SAML or OpenID Connect.
- Protocols
- SAML and OpenID Connect (OIDC).
- Roles
- Groups in your identity provider map to roles in Strive.
- Systems
- API keys.
- Rate limits
- Requests are limited for each organization.
Role-based access
Role-based access control: each person has a role, and the role decides which apps, data and actions they can use. The Assistant works with the same access as the person using it, so it can only see and do what they can.
- Roles
- Assigned to each person, or mapped from groups in your identity provider.
- Apps and data
- A role decides which apps, records and actions a person can use.
- The Assistant
- It has the same access as the person using it, no more.
- Changes it proposes
- They wait for someone with the right role to approve them.
- Actions that cost money
- They ask for confirmation first.
- Organizations
- Each organization's data is kept separate.
Questions
What people ask about hosting.
Can we run it in our own cloud?
Yes. Strive runs in our cloud, or in your own VPC on AWS, Google Cloud or Oracle Cloud, or on your own Kubernetes cluster.
Is there an uptime SLA?
Yes, on every agreement, along with a named support contact.
Will you help with our security review?
Yes. We share our SOC 2 Type II report, answer your questionnaire and give your team time with our engineers.
Which plan includes single sign-on?
Enterprise, along with SCIM. Single sign-on works with Okta, Entra ID, Google Workspace or any provider that supports SAML or OpenID Connect.
Where does our own code run?
In isolated containers with limits on what they can reach on the network. Apps run the same way.
How do we install it in our own environment?
With Helm, into your own Kubernetes cluster. The cluster can be in your cloud account or on your own hardware.
How long is run history kept?
As long as your agreement sets, and you can export the audit log.
Which document-heavy job would you hand over first?
Bring one process you want to improve and the information behind it. We build the first version with you in the session, so the first thing you see is your own work, running.
Contact SalesAn hour of your time and a process you know well. That's all it takes.