Senior Sales Engineer - Enterprise

Viral AI assistant Instinct now has its own email address. Instinct's new email feature lets the AI agent create and manage accounts, contact businesses, handle support requests, and do more on users' behalf. Instinct, the buzzy new AI assistant now valued at $2.5 billion, is rolling out a new feature that will allow it to do more on its users' behalf: It's giving everyone Instinct email addresses. The company's founder, Noah Shinn, said on Tuesday that the new email addresses let the agent create and run its own accounts without cluttering up users' inboxes. Shinn said the idea is to allow Instinct to handle the account sign-up and management for you if it needs to do so for completing tasks that require email, like creating accounts on various services, contacting businesses, and following up on things that need attention. "For example, Instinct can use its own email to contact a restaurant about a special request, ask a business about availability, or sign up for a service it needs to complete your task," Shinn wrote on X. IntelPro is giving Instinct access to more tools. Starting today, your Instinct will have its own email address. This is the first step towards enabling your Instinct to own and run its own accounts. Most everyday tasks flow through your email: creating accounts, confirming bookings,... pic.twitter.com/brwQSsJnmJ Noah Shinn (@noahrshinn) September 8, 2026 The feature could help make Instinct's user experience more seamless, as users wouldn't have to intervene to log in or provide their credentials. (Instinct partnered with 1Password on the latter last week.) But for businesses trying to establish a relationship with their customers, having an AI manage the account would provide a layer of obscurity as to who they're actually dealing with. Customers, however, may see this as a perk, as many are these days tired of having to turn over their emails and phone numbers just to complete simple tasks or one-offs. Instinct says it has reserved some email addresses for its earliest users, and others can claim theirs at mail.instinct.com. Shinn suggested that users could now forward emails to Instinct, too, when it needs certain information to complete a task. For example, if a user wants Instinct to handle a product return on their behalf, they could forward their order confirmation to Instinct's email address. Then Instinct could contact support, provide the order details, ask whether they wanted a return or replacement, and then come back with the return label to print. Instinct's email can also be added to group threads so it can keep track of the information exchanged, or it can be sent a long thread that the user needs to work with, perhaps by asking what decisions still need to be made, which tasks are due when, or other questions. The bot will check back in with the user when it requires their input, but otherwise will act autonomously. The feature is one of several recent updates aimed at improving Instinct's capabilities. It follows the recent partnership with 1Password to help enable logins to users' existing accounts, as well as a new location-sharing feature that lets Instinct understand where the user is currently so it can help them find nearby businesses or restaurants, or map routes and itineraries, among other things. Users can also ask questions about their location history, like where they parked or what restaurant they tried last month. Instinct also partnered with Stripe in August to offer a more seamless payment experience, letting the agent do things like book trips, classes, and appointments and make purchases.

1Password just pledged $300,000 to DHH's Omarchy, and its own employees aren't happy. Internal Slack messages show the CEO and cofounder gave staff two very different explanations for the decision. Omarchy has been on something of a roll now. Funding for its foundation has been climbing fast, from an $8 million launch to $10 million a few weeks later, and now crossing $13 million with the most recent pledge. What's drawn my attention are the first two Corporate Patrons, 1Password and 37signals, both of whom have decided to pitch $100,000 a year for the next three years. Now, 37signals I get; DHH is heavily involved there, but 1Password was a surprise entry. Naturally, not everyone's onboard with their pledge. Signs of disagreement. This has not gone well with employees working at 1Password, with company leadership having to take certain damage control measures to assure their staff. An internal Slack message has surfaced (courtesy of The Verge), which shows cofounder Roustem Karimov downplaying the criticism, telling team members that: people have different personal opinions. You believe in your heart that DHH is evil, that you have the moral high ground, and that nothing will change your mind. However, not everyone believes that. It is not fair to claim a monopoly and ostracize team members who might disagree with you. There are people who are afraid to speak up simply because they will be personally attacked. CEO David Faugno responded on a different note, telling employees the company doesn't endorse DHH's views, while also noting that Omarchy is the second most used Linux distribution among 1Password's own users. Why the backlash? DHH is known to be someone who firmly falls on the "right" side of the political spectrum, someone who doesn't shy away from putting his opinions in public view. He regularly posts blogs that show where he stands on certain societal issues, and some of his recent writeups are what's fueling this particular backlash. His recent July post, titled "Wolves, sheep, and gypsies," compares Denmark's wolf population with the Romani people camping in Copenhagen parks, where he argues: "When gypsies take over public spaces, you deport them." Then there's "As I remember London" from September 2025, where he laments about London losing its native Brit majority and a nod of approval for a Tommy Robinson march. Of course, these aren't the only factors behind his disapproval, but you get the gist of it, right? Users could jump ship. If you search for the terms "1Password" and "Omarchy" right now, you are bound to run into the many comments made by disgruntled 1Password users on Reddit and Hacker News. They are calling the choice tone-deaf, given how many smaller open source projects could've benefited from the money. Some are already jumping to alternatives like Bitwarden, while others suggest self-hosting Vaultwarden or going with KeePass and its forks instead. I see the issue compounding too. Back in February, 1Password raised subscription prices, taking effect at renewals from March 27. Individual plans went up 33 percent from $35.88 to $47.88 a year, and family plans went up 20 percent from $59.88 to $71.88. Its community forum already has a long thread full of longtime users saying they were leaving over it. If 1Password continues playing with its users' trust like this, who knows what kind of exodus it will see next? Enjoyed this update? Support independent Linux news coverage It's FOSS has been helping people use Linux for the past 14 years. Help Ubo stay independent from big tech. Become a Plus member, enjoy ad-free reading and get 5 eBooks. Plus yearly Best value Plus lifetime Pay once, Enjoy forever Buy Ubo a coffee Any amount, no commitment A nerd with a passion for open source software, custom PC builds, motorsports, and exploring the endless possibilities of this world.

Managing secrets securely in Kubernetes with 1Password. 02.09.2026 Reading time: 4 mins. Last Updated: 02.09.2026 Table of contents. Managing secrets securely in Kubernetes is a critical challenge for modern cloud-native environments. Application credentials, certificates, private keys, and passwords must be handled in a way that is secure, auditable, and operationally flexible - especially when regular rotation is required. By integrating 1Password with Kubernetes using the External Secrets Operator (ESO), teams can centralize secret management while keeping sensitive data out of Git repositories and Kubernetes manifests. This approach enables Kubernetes workloads to consume secrets securely while maintaining strong access control and rotation practices. Architecture overview: 1Password + Kubernetes. The 1Password integration with Kubernetes works by introducing an abstraction layer between Kubernetes and the 1Password cloud API. Instead of Kubernetes communicating directly with 1Password's cloud service, a 1Password Connect Server runs inside the cluster. This design provides better security, performance, and control. * Kubernetes communicates with the External Secrets Operator * ESO talks to the 1Password Connect Server inside the cluster * The Connect Server authenticates to 1Password using a token * Requested secrets are fetched and returned to Kubernetes This architecture allows secrets to be synced securely into Kubernetes-native Secret objects. Step 1: install External Secrets Operator and configure ClusterSecretStore. To begin, you must install the External Secrets Operator in your Kubernetes cluster. ESO provides the Custom Resource Definitions (CRDs) required to define how Kubernetes connects to external secret providers. The most important CRD in this setup is the ClusterSecretStore. It is a cluster-wide resource that defines how Kubernetes authenticates and communicates with 1Password. Example configuration: kubectl get ClusterSecretStore/ie-onepassword -o yaml apiVersion: external-secrets.io/v1 kind: ClusterSecretStore spec: conditions: - namespaceSelector: matchLabels: bango.com/dept: Engineering provider: onepassword: auth: secretRef: connectTokenSecretRef: key: token name: onepassword-connect-token-ie namespace: ns-dev-external-secrets connectHost: http://onepassword-connect.ns-dev-1password-connect-server.svc.cluster.local:8080 vaults: Engineering DevTest: 1 This configuration instructs ESO to communicate with the 1Password Connect Server rather than the public 1Password API. The Connect Pod authenticates using a token and retrieves secrets from the specified vault. Step 2: create externalsecret resources for applications. To consume secrets inside an application - for example, a service that uses a client certificate to authenticate to a remote endpoint - you must define an ExternalSecret resource. apiVersion: external-secrets.io/v1 kind: ExternalSecret metadata: labels: env: dev name: dev-cert-external-secrets-even namespace: ns-dev-engineering-korek spec: data: - remoteRef: key: CERT Engineering|endpoint|Cert|dev 20260626 property: endpoint_dev_CERT_PUBLIC.pem secretKey: CERT_PEM - remoteRef: key: CERT Engineering|endpoint|Key|dev 20260626 property: endpoint_dev_KEY.key secretKey: CERT_PRIVKEY target: name: dev-external-secrets-even creationPolicy: Owner deletionPolicy: Retain Key Concepts Explained * remoteRef.property specifies the exact entry inside 1Password to be retrieved. * Applications cannot reference ExternalSecret objects directly. * The target section defines the Kubernetes Secret that ESO creates and keeps in sync. This target secret is what applications ultimately consume. Supporting certificate rotation with even/odd secrets. To enable safe certificate and key rotation, it's recommended to maintain two ExternalSecrets: * dev-external-secrets-even * dev-external-secrets-odd This approach allows: * Seamless certificate rotation * Zero-downtime updates * Easy rollbacks by switching references When a rotation cycle is approaching, new certificates can be added to 1Password and synced to the inactive ExternalSecret without impacting the running application. Understanding creationPolicy and deletionPolicy. Two fields require special attention: creationPolicy: Owner * ESO creates the Kubernetes Secret if it doesn't exist * ESO updates the Secret whenever the external value changes * Deleting the ExternalSecret deletes the target Secret Alternatively, Merge can be used when multiple controllers manage the same Secret. deletionPolicy: Retain * If a secret is accidentally removed from 1Password, the Kubernetes Secret remains * Prevents accidental outages caused by human error * Recommended for production workloads Step 3: verifying externalsecret health. kubectl -n ns-dev-app get externalsecret NAME STORETYPE STORE REFRESH INTERVAL STATUS READY dev-app-external-secrets-even ClusterSecretStore ie-onepassword 5m SecretSynced True dev-app-external-secrets-odd ClusterSecretStore ie-onepassword 5m SecretSynced True Updating secrets in 1Password automatically updates the corresponding Kubernetes Secret without disrupting the application. Step 4: mount multiple secrets using projected volumes. To make both certificate sets available in the same directory inside a container, you can use a projected volume. This allows multiple secrets to be mounted into a single path. Example using Flux and Kustomize: patch: |- - op: add path: "/spec/template/spec/volumes/-" value: name: app-keystore-cert projected: sources: - secret: name: dev-app-external-secrets-odd items: - key: TEST_PEM path: app_keystore-odd.pem - key: TEST_PRIVKEY path: app_keystore-private-odd.pem - secret: name: dev-app-external-secrets-even items: - key: TEST_PEM path: app_keystore-even.pem - key: TEST_PRIVKEY path: app_keystore-private-even.pem The final step is simply configuring the application to reference the appropriate file inside the container. Final thoughts. Using 1Password with Kubernetes via the External Secrets Operator provides a secure, flexible, and production-ready approach to secret management. This setup enables: * Centralized secret storage * Safe certificate rotation * Reduced blast radius from human error * Kubernetes-native secret consumption For teams operating at scale, this approach significantly improves both security posture and operational reliability. Check out more of its blog posts here. Signal, not noise -. Join 12,000+ engineers and business leaders getting field notes on SRE, DevOps and cloud- native reliability. Your work email. More posts. Encryption is one of the first security controls FinTech companies think about when discussing PCI DSS. Sensitive data is encrypted at rest. Connections use TLS. Payment information is tokenized. Cloud... Expanding an iGaming business into a new regulated market is rarely as simple as obtaining a new license. Every jurisdiction comes with its own regulatory expectations, technical requirements, security controls,... Get In Touch ITGix provides you with expert consultancy and tailored DevOps services to accelerate your business growth.