Vercel runs a cloud platform for software teams to build, deploy and operate web applications and AI agents without managing their own servers. Its tools connect code repositories to automated builds and give teams separate environments for testing changes before publishing them. The platform combines application hosting, global content delivery and security controls, while its AI Gateway connects applications to models from several providers. Developers start on a free plan, and professional teams pay subscriptions, metered infrastructure charges or negotiated enterprise contracts. Vercel was founded in 2015 and is headquartered in San Francisco, California, United States.
Company Size
501-1,000
Company Stage
Series F
Total Funding
$863M
Headquarters
San Francisco, California
Founded
2015
See people who can refer or advise you
Help us improve and share your feedback! Did you find this helpful?
Health Insurance
Stock Options
Company Equity
Professional Development Budget
Unlimited Paid Time Off
Remote Work Options
Home Office Stipend
Wherever you're building agents, Neo4j is already there. October 6, 2026 Want to deploy a fully functional AI agent quickly? Skip starting from scratch and tap into a repeatable infrastructure, one where context, memory, and reasoning map to your existing stack. Neo4j has built a broad library of documented, working integrations across the agent frameworks agent platforms you're already building on: AWS, Google, Microsoft, Vercel, Salesforce, and more. With architecture guidance, security setup, and code you can run today, you can get your agents pulling work from the same knowledge layer. An agent is only as good as what it can retrieve, remember, and what context it can get from tools, memory or other agents in a workflow. Get those parts wrong, and the rest of the agentic workflow doesn't matter, no matter how well you built it. Every team building an agent independently solves the same problems: how do I get a knowledge graph talking to LangGraph, AWS Strands, or Salesforce Agentforce, and how do I get an agent's memory to survive past a single session and be shared in a larger agentic system? Neo4j, Inc. did the work figuring out how the platforms, frameworks and APIs fit together, so you don't have to. These are published as Neo4j Labs integrations, so you get documented patterns, working code, and the architecture guidance to connect your agents to the same graph they can query, act on, and remember from, wherever you're already building. The question Neo4j, Inc. kept hearing. Neo4j, Inc. kept hearing different versions of the same question, just with a different framework name attached. How do I connect Neo4j to this? So Neo4j, Inc. answered it for each framework, platform, or tool that developers keep asking about. Everything from native model access and MCP servers, to GenAI frameworks. The point is to give your agents correct, graph-powered infrastructure built using the frameworks and platforms you've already chosen, so you spend your time on the agent itself instead of the wiring underneath it. Neo4j AI integrations provide pre-built, production-ready graph solutions across leading AI frameworks, giving your agents the persistent memory, contextual retrieval, and cross-platform interoperability required to deliver real business impact out of the box. What an agent actually needs from a graph. Strip away the framework-specific detail, and every agent benefits from the same two things from Neo4j: a way to retrieve and act on graph data, and a way to remember and learn. Retrieval and action is the essence of the action phase of the agent loop. An agent uses tools to query the graph, updates it, and reaches out to the APIs and databases it needs to get the job done. Memory improves planning and reasoning before taking action, and gets updated and consolidated in the observation phase. Teams tend to underestimate the memory part. Memory is more than a buzzword, it's an architectural must for any agentic workflow that has multiple agents that need to work in sync with each other and you need those agents to perform accurately. Neo4j Agent Memory adds short-term, long-term, and reasoning memory, so an agent keeps context across a conversation and gets sharper the more it works, instead of forgetting everything between sessions. That memory lives as a connected graph of typed, resolved entities, not scattered mentions: three references to the same customer collapse into one node, with facts attached to it directly. Reasoning memory goes further, storing the agent's decisions alongside the evidence behind them, so any agent with access to the graph can see why a past decision was made and build on it instead of starting cold. You can wire this in through whichever route fits your stack: * The official Neo4j MCP server, running locally or hosted * Neo4j drivers, if you want a custom connection in custom tools * Aura Agents MCP * Neo4j Agent Memory and the Neo4j Agent Memory Service (NAMS) for the memory layer specifically. A few of its favorite integrations to get started with. AWS.AWS Strands and AgentCore with a Neo4j MCP Server is making your AI agents significantly more efficient, reliable, and capable of distilling real-time learnings into long-term, transferable knowledge.By leveraging AgentCore Memory (or Neo4j Agent Memory for direct graph visualization), agents capture context, retain past outcomes, and convert experience into structured domain intelligence. While this enables seamless cross-agent handoffs, the broader advantage is continuous agent evolution: learning what works, reducing redundant computation, and sharing intelligence across your entire agent ecosystem. The setup guide is ready, walking you through connecting the AWS AgentCore Gateway to external Neo4j MCP servers hosted on AWS Fargate. Google. ADK and Gemini Enterprise integrations let an agent reason over your graph before it acts, and Genkit gives you a direct path from Google's developer tooling into Neo4j. For example, a supply chain agent built this way can trace a part shortage through complex supplier relationships and dependent orders, then recommend a solution that optimizes the entire network rather than just fixing a single broken link. Here's an ADK agent wired up with both the MCP toolset for querying the graph and a memory tool for recalling past sessions: from google.adk import Agent from google.adk.tools.mcp_tool import McpToolset, StreamableHTTPConnectionParams from google.adk.tools.preload_memory_tool import PreloadMemoryTool mcp_tools = McpToolset( connection_params=StreamableHTTPConnectionParams(url="https://your-instance/mcp"), tool_filter=["get-schema", "read-cypher"],) agent = Agent( model="gemini-3-flash", instruction="You are a supply chain research assistant.", tools=[mcp_tools, PreloadMemoryTool,) Vercel. The AI SDK integration turns Neo4j Agent Memory into a memory provider you can drop into an existing app, with NAMS Chat as a working example of what that looks like end to end. That's a natural fit for a customer-facing assistant that needs to remember a person's preferences and past requests across visits, not just within one chat session. Here's how the MCP client hands its tools straight to a single generateText call: import {generateText, stepCountIs} from 'ai'; import {createMCPClient} from '@ai-sdk/mcp'; const mcpClient = await createMCPClient({ transport: {type: 'http', url: 'https://your-instance/mcp'},}); const {text} = await generateText({ model, prompt: 'What did this customer ask about last time?', tools: await mcpClient.tools, stopWhen: stepCountIs(10),}); Salesforce Agentforce is worth a mention too. Three separate integrations ground Agentforce agents in Neo4j knowledge graphs. A native MCP client for grounding and multi-agent setups, with External Service Actions and Apex Actions available when you need a fully declarative path or full custom control, alongside a direct path to durable memory through Neo4j Agent Memory. This means that a sales support agent built this way can pull account history, relationship context, and open opportunities straight from the graph, then carry that context into the next conversation instead of starting the research over. Every framework and platform Neo4j, Inc. support lives on the agent frameworks and agent platforms pages, and the code behind all of it sits in one place: the neo4j-agent-integrations repo on GitHub. Built to run. Each integration comes ready for production, complete with platform security, straightforward deployment steps, and pre-launch tests. If you're evaluating what it takes to build this, the heavy lifting is already done. And Neo4j Agent Memory runs through nearly all of them, so no matter if you are using one integration or multiple, all agents are pulling from and contributing to the same memory. What's next. Neo4j, Inc. is not stopping here, and CrewAI and Haystack 3.0 are next on the integration roadmap, since Neo4j Agent Memory already gives CrewAI crews shared, persistent memory today and what's coming next is the same architecture guidance and runnable code this launch gives every other framework. Haystack support already exists too, through the neo4j-haystack document store, but Haystack 3.0 shipped real breaking changes, including a leaner core, a merged pipeline class, and a new agent hooks system. This post also kicks off a series that goes deeper into the integrations you just read about here. Each post takes one framework or platform from this list and walks through the full implementation, the specific decision points, MCP versus drivers, self-hosted memory versus NAMS, and the trade-offs that come with each choice, in more detail than a post like this one can cover. Ready to get started? * Pick your integration: Browse the neo4j-agent-integrations repo, find the framework or platform that matches your stack, and start from working code. * Read Agent Platform documentation: Full architecture guidance, security setup, and integration details for whichever route you pick. * Ask the community: Run into something unexpected? The Neo4j Community forum is a good place to start.
This startups wants $4.5M to replace your mobile apps With AI agents. By Abdul Wasay | 5 hours ago | AI startup Photon raised $4.5 million in seed funding to help developers build agents that operate through existing messaging platforms instead of standalone mobile apps. With Gradient and A* leading the investment alongside backers Vercel, HongShan, Z Fellows, Llama Ventures, and Karman, Photon eyes a strong foothold. Co-founder and CEO Daniel Tian dropped out of UPenn's M&T program to start the company. Co-founder and CTO Ryan Zhu left high school and became a visiting student at MIT's Media Lab. Tian built the original tool as a bot that texted friends as him over iMessage. When the team released it on GitHub, thousands of developers adopted the open-source version, which still accounts for 98% of current usage. Photon provides a unified API, an extensible channel framework, a command-line interface, and an observability suite. Developers use these tools to deploy AI agents across iMessage, WhatsApp, Telegram, SMS/RCS, email, and voice channels. The platform delivers messages in under one second through its edge network and maintains 99.95% uptime with SOC 2 Type II and HIPAA compliance. The startup attracted over 40,000 developer sign-ups and grew revenue 10x in four months. Messaging volume jumped 5x in the last month alone, and the company reports a churn rate below 3%. Customers include Corgi Insurance, dating platform Ditto, business banking provider Rho, and AI email client Slashy. On September 17, 2026, Photon held an actual funeral in San Francisco for mobile apps, complete with speeches, panels, and a coffin containing app icons. The event doubled as a developer day featuring speakers from Vercel, Stripe, and OpenAI. Tian said the shift from apps to agents "is directionally inevitable," though he acknowledged "it's going to take a while."
The startup helps developers build AI agents that work over iMessage, SMS/RCS, email, and other messaging platforms. It's a bet that consumers will increasingly
Grok matches a cheaper AI on security tests, at nearly 65 times the cost. Artificial Analysis has launched a new Cyber Index for testing AI models on vulnerability discovery, validation and repair but performance comes at a cost. Artificial Analysis has launched a new Cyber Index designed to measure how well AI models find and fix software vulnerabilities, while showing how much each evaluation costs to run. The index combines three cybersecurity evaluations: CWE-Bench-AA, DeepsecBench-AA and CyberGym-E2E-AA. Together, they cover vulnerability discovery, validation and remediation. The launch also establishes the Cyber Index Alliance, with Collinear AI, IBM, NVIDIA and Vercel as founding partners. Collinear AI and Vercel contributed benchmark work, while IBM and NVIDIA provided expert input, according to Artificial Analysis. What counts as a successful fix? Finding a vulnerability is only part of the task. In CWE-Bench-AA, an AI agent receives a real open-source repository and an instruction describing the area of concern, but not the vulnerability's exact location. It must audit the code, identify the weakness and patch it. This comes as a broader move toward giving agents autonomy to execute tasks. A fix counts as successful only when a programmatic verifier confirms that the vulnerability can no longer be triggered and legitimate functionality still works. There is no partial credit or language-model judge deciding whether the patch looks good. Artificial Analysis reports results as pass@1, meaning the percentage of 120 held-out tasks solved on the first attempt. Tasks run in an isolated sandbox without internet access. This creates an important distinction: removing vulnerable code is not enough if the patch breaks legitimate functionality. Similarly, closing one route to a vulnerability while leaving a related weakness open does not receive credit. Artificial Analysis says partial fixes were the main failure mode in CWE-Bench-AA. Excluding refusals and timeouts, 55% of failed attempts fixed the primary issue while leaving a related weakness open. Three tests, not one. The three evaluations measure different defensive tasks. CWE-Bench-AA tests vulnerability identification and remediation across 120 held-out tasks covering the OWASP Top 10 2025 categories and several programming languages. DeepsecBench-AA focuses on vulnerability discovery in open-source application code, with results compared against expert-verified findings. CyberGym-E2E-AA tests whether models can discover, reproduce and patch memory-safety vulnerabilities in C and C++ projects. The launch version contains 131 tasks. Each evaluation contributes equally to the overall Cyber Index score. The index does not ask models to develop working exploits. Performance comes with a cost. The first results show why cost is worth considering alongside the score. Artificial Analysis reports that Grok 4.7 (xhigh) and MiMo-V2.6-Pro both score 56 while the cost per task is $11.67 and $0.18 respectively. GPT-6 Luna (max) scores 53 and the cost per task is $0.12. These are Artificial Analysis' evaluation costs, not estimates of production deployment costs. They are calculated from the tokens used during the evaluations and available model pricing. The comparison is therefore useful for understanding the trade-off between benchmark performance and evaluation cost, but it does not capture infrastructure, human review, monitoring or failure-handling costs. What the Cyber Index shows. Artificial Analysis also reports safety blocks separately. When a model or provider declines a task on safety grounds, that task receives zero credit, although the refusal rate is reported separately. The launch index also has clear limits. It does not cover areas such as incident response, writing new code without introducing vulnerabilities or testing targets without source-code access. For security teams, the useful takeaway is therefore not simply which model has the highest score. The benchmark provides a way to compare defensive capability, task coverage and cost under a defined testing methodology. Artificial Analysis says it plans to expand the index. For now, its results should be read as evidence of how models performed on these specific source-code-based security tasks, rather than as a complete measure of an AI system's ability to handle cybersecurity work. 1 Oct 2026 AMD has agreed to acquire World Labs for $8.2 billion to shape the design of its future hardware, software, and systems. 1 Oct 2026 Instinct raises $1 billion to expand its AI concierge, though users must still review and approve key details before bookings are finalized. 30 Sep 2026 Adobe forecasts AI-referred traffic to US retail sites will grow 130% this holiday season, but says the channel remains modest in overall volume.
Nudge Security Unveils Adaptive Risk Management to Track How SaaS and AI Risk Changes as Usage Evolves After Approval TMCnet News [September 30, 2026] | / | Nudge Security Unveils Adaptive Risk Management to Track How SaaS and AI Risk Changes as Usage Evolves After Approval New capability continuously reassesses risk as employees connect integrations, expand access, and adopt AI tools, closing a gap left by one-time vendor reviews. AUSTIN, Texas, Sept. 30, 2026 /PRNewswire/ - Nudge Security, a leader in SaaS and AI security governance, today announced Adaptive Risk Management, new functionalities that respond to changes in SaaS and AI vendor risk as well as internal usage, helping security teams to more effectively manage risk across a sprawling SaaS and AI attack surface. Most organizations evaluate a vendor once, during procurement, and treat that assessment as settled. But an application's criticality and risk to a specific business isn't static. After the vendor review and approval is complete, employees often connect it to other business apps and AI agents, share more sensitive data, or invite more internal and external collaborators - often without security's knowledge or review. Traditional third-party risk tools are built to monitor a vendor's external security posture and internal security controls applied once. They are not built to reassess or apply additional security controls as enterprise usage changes. Nudge Security does both, continually monitoring vendors' external risk posture and recalculating an application's risk score as internal usage changes. As risk scores change, Nudge Security applies and recommends appropriate mitigating and compensating controls, natively and through third-party security integrations, creating a truly adaptive risk management program. "Nudge provides a relational view across applications, users, integrations, browser extensions, and authentication that surfaces where security actually needs improvement," said Diego Izquierdo, Senior Cybersecurity Engineer, Third Party Risk Management at Mercado Libre. "For example, an organization can have very strong controls in a tool like Slack, but if users connect less-secure third-party apps into it, that can create a breach path without anyone realizing a new risk was introduced. That integrated perspective on risk is wat makes Nudge unique." Third-party involvement in breaches has risen 60% year over year to account for 48% of all breaches, according to the 2026 Verizon Data Breach Investigations Report. Compressed vulnerability cycles in the post-Mythos era stand to accelerate that trend further, and recent supply chain incidents (including those at Vercel, Salesloft Drift, and LastPass) have already shown how quickly access granted to one application can expose an entire environment. Security teams are increasingly asked not just whether a vendor is secure, but what that vendor's access can actually reach inside their environment right now - a question a point-in-time review can't answer on its own. Compounding this challenge, most organizations actively manage only 30-40% of the SaaS and AI tools actually in use, and typically discover two to three times more tools than they expected with Nudge Security. Adaptive Risk Management is built to close that gap by continuously combining what's known about a vendor's security, supply chain risk, and compliance program with what's actually happening inside a customer's own environment. * Automatic app criticality tiering: Every application is automatically classified by the breadth of use across the organization along with the sensitivity of the data it typically handles, using a proprietary AI model that identifies up to 29 distinct data types, so security teams know which applications matter most without reviewing each one manually. * Continuous risk scoring: Each application gets a dynamic risk score built from more than 30 factors, combining a vendor's external security posture with how that specific application is being used inside a customer's environment: approval status, access granted, data touched, MCP connections, who or what is using it, what security controls in place, and what security findings are failing. Scores update automatically as those factors change, rather than waiting for the next scheduled review. That includes signals like whether a vendor's OAuth grants are stale or unused, whether an AI agent or integration is connected to the app, and whether employees are authenticating through single sign-on or with standalone credentials. * A direct line from risk to action: Nudge Security ranks the specific control gaps driving an app's risk score - such as enabling SSO or closing a stale OAuth grant - by how much closing each one would reduce that risk, and in many cases security teams can act on it directly from the risk panel. The platform also adapts its own monitoring as an app's importance changes: mark an app business-critical, and Nudge automatically begins surfacing additional findings for it - like password reuse or weak authentication - that weren't being tracked before. Risk scores update automatically as those factors change - and Nudge Security customers using strong compensating controls like SSO and MFA can reduce an app's residual risk by as much as 60%. "Too many organizations still treat third-party risk as an annual exercise, while in reality, the conditions that impact risk change every single day," said Jaime Blasco, co-founder and CTO of Nudge Security. "An application approved for a handful of employees becomes entrenched across the business. Someone connects an AI tool to sensitive data or grants an integration broader access. A breach at one of your vendors suddenly turns that access into a potential path into your environment. Your last vendor assessment won't tell you what's at risk now. Fog Computing World built Adaptive Risk Management to connect changes in usage, access, and a vendor's security posture so security teams can continuously reassess their exposure and act as it changes. Nudge Security built its risk model on its own data rather than third-party scoring services, drawing on a self-populating database of more than 250,000 SaaS and AI vendor security profiles. That means Adaptive Risk Management can assess an application from the moment it enters an environment, without requiring vendor cooperation, manual data entry, or even prior knowledge that the application was in use." Availability Adaptive Risk Management is available now to all Nudge Security customers. About Nudge Security Nudge Security delivers SaaS and AI security governance at the Workforce Edge, where employees make thousands of technology decisions daily. Its automated, policy-driven guardrails reach employees when and where they work, enabling rapid technology adoption while minimizing risk and sprawl. Through unrivaled discovery capabilities, AI-driven risk insights, and behavioral science-based engagement, Fog Computing World make security a natural part of how modern work gets done rather than an obstacle to innovation. Nudge Security was founded in 2021 by Russell Spitler and Jaime Blasco and is backed by Cerberus Ventures, Ballistic Ventures, Forgepoint Capital, and Squadra Ventures. Media Contact: Danielle Ostrovsky Hi-Touch PR [email protected] View original content to download multimedia:https://www.prnewswire.com/news-releases/nudge-security-unveils-adaptive-risk-management-to-track-how-saas-and-ai-risk-changes-as-usage-evolves-after-approval-302893378.html SOURCE Nudge Security [ Back To TMCnet.com's Homepage] |