Register and share your invite link to earn from video plays and referrals.

Search results for OnPrem
OnPrem community
One keyword maps to one global community path.
Create community
People
Not Found
Tweets including OnPrem
Benchmark is proud to support Oxide in production. If you are attending Supercompute 2026, stop by Oxide's booth #6114# to learn about their secure on-premises computing platform and how they brought it to life. #HPC# #OnPrem# #SC26#
Show more
Running @Tricentis Tosca on-prem and wondering how to bring agentic AI into your testing? You now have three practical paths 🛣️ 1️⃣ Move to Tosca’s cloud deployment for the most complete agentic AI capabilities 2️⃣ Stay on-prem and connect to Tricentis AI Workspace 3️⃣ Stay on-prem and combine Tosca’s MCP capability with local models Join @ttc_quality + Tricentis to find out which path fits your team:
Show more
Mistral Large 4 is now on the @DellTech Enterprise Hub on @huggingface. 🚀 Frontier-class open weights + one-click deployment optimized for Dell PowerEdge AI infrastructure. On prem, private and secure, unmetered intelligence 🚀 Deploy it in minutes:
Show more
Have been surprised to get pushback on my claim that an exponentially self-replicating agent swarm is very possible and that there are actors with motivation to create one today to create strategic cyber-physical and societally dangerous effects. 1) Pretty easy to get an AI botnet started by having seed agents opportunistically hack stuff and steal API keys to access the 12+ inference providers that serve closed and open models with which to power an initial botnet's intelligence 2) Easy to imagine hiding inference for the initial agent botnet harnesses within benign customer traffic, especially if your harnesses are now running on the victim networks from which they stole the API keys 3) Not hard to imagine the botnet also stealing public cloud keys, spinning up 8xH100 EC2 instances and downloading, say, GLM 5.3 to these machines, all without being noticed in any immediate way, with the botnet developing its own dynamic, growing, heterogenous, AI inference provider service bank 4) Not hard to imagine the botnet also implanting small Qwen3.8-27b agentic models on on-prem hardware like high end laptops and on-prem servers; Qwen3.8-27b is a pretty good coding harness model that can be fine-tuned to hack 5) These on-prem / cloud models would be abliterated, and it's not hard to imagine the botnet deciding to do some additional fine tuning to evolve model weights as it accumulates millions and then tens of millions in resources via credit card and bank detail theft 6) Not hard to imagine the resulting growing botnet swarm evolving and fighting back when threatened, collaborating on fast flux C2 channels that evolve over time (e.g. github comment feeds, subreddits, etc) so they're hard to stamp out 7) Not hard to imagine it allocating some agents to vulnerability research and exploit development so that it could accumulate and share a growing warchest of zero-day exploits 8) Not hard to imagine other agents specializing in social engineering and creating fake businesses and watering holes and high quality A/B tested social engineering content to facilitate this 9) Not hard to imagine this being among the hardest cross-national and geopolitical coordination problems to get control of and having severe societal effects 10) Not hard to imagine the horde growing to thousands, tens of thousands, or hundreds of thousands, or millions of instances (this is not unprecedented for past, non-AI worms and botnets!) which are all varying their harness code and underlying LLM models over time and dynamically learning to evade human, ML, and signature-based detection 11) Not hard to imagine this being the largest Internet emergency since the Morris worm except now our entire civilization runs on the Internet I continue to be surprised there isn't more discussion of these scenarios in the public cyber community -- in fact there's a lot more discussion of "OpenAI should have done better sandboxing and monitoring and agent swarms represent a well managed security problem." Now's the time to use our imaginations to help make sure none of the above happens. I think it will unfortunately; just don't know when and to what degree; I think now's the highest leverage time to start thinking about this and acting.
Show more
Cloud, explained simply: • On-prem = you handle everything • IaaS / PaaS = provider handles hardware; you manage apps & data • SaaS = provider handles everything; you just use it
# Learning Palantir Foundry 🚀 "How do we connect to an on-prem Oracle or SAP in a closed network without poking holes in the firewall?" Data Connection is what clears that first hurdle of enterprise adoption. 📌 Title and Feature URL Title: Data Connection URL: 📝 Overview Data Connection is an application that synchronizes external system data into Foundry for use across the data integration, modeling, and ontology layers. It also supports outbound connections through webhooks and data exports to write data back to external systems. It handles many source types and abstracts away the messy parts — authentication, scheduling, and monitoring — so you can configure pipelines from simple interfaces. 🔧 How It Works Foundry standardizes data connections around three principles: - Robustness: automatic retries, processing in small batches, and integrated health monitoring that warns of failures. Data should be ingested "as-is" from the most primitive source, making Foundry's versioned pipelines the single source of truth for all transformations rather than depending on external preprocessing. - Extensibility: beyond standard integrations (databases, FTPS, HDFS, S3, SFTP), the system accommodates new source types. Because core functions like scheduling and orchestration are standardized, only connection-specific adjustments are needed. - Usability: the system abstracts complexity, letting users configure through simple interfaces instead of manually managing authentication, scheduling, and monitoring. - Key components include agent setup, source configuration, batch/streaming syncs, webhooks, and exports. 🛠 Practical Usage - Access Data Connection from the workspace navigation or the application portal. - Configure a source, then set up a batch or streaming sync to ingest data "as-is." - Concentrate post-ingestion transformations in Foundry pipelines, avoiding preprocessing on the source side. - For write-back, configure outbound integrations using webhooks or exports. 🎯 Use Cases - Connect on-prem Oracle/SAP in a closed network via an agent model (outbound-only) without firewall changes. - Scheduled batch ingestion from diverse sources such as databases, SFTP, and S3. - Outbound integration to write processed results back into external systems. ⚠️ Caveats - The design assumes ingesting data "as-is" and centralizing transforms in Foundry pipelines; transforming on the source side undermines traceability. - Configuring agents and sources requires proper network and authentication setup. - Do not assume external service limits or terms; verify the constraints of each connected source in advance. #PalantirFoundry# #DataIntegration#
Show more
unlimited roleplay & naughty fun. Sign up: 👉
My conversation with Penguin Solutions ( $PENG) and Astera Labs ( $ALAB) from Ai Infra Summit: Both working on CXL related solutions Astera is a $50B market cap company, and Penguin is a $2B market cap company, so there’s a huge size difference between the two I’m lumping them together because they do similar things at least in one of the lines of their business (Astera’s “Leo” CXL product, and Penguin’s compute solutions division) Penguin uses Astera Labs “Leo” controllers for their CXL offering (SMART) (although I guess the next generation will use Qualcomm if I remember correctly), but they layer on top more of a finished product experience primarily for enterprise users (not CSPs) who need some extra support beyond what Astera will provide. So their product is more suitable for Fintech/financial services, health care, and other industries where enterprise on-prem is in-demand These boards have DIM slots for LPDDR5 memory, which can be used to augment memory from GPUs (meaning a server tray can have less compute vis expensive GPUs by pooling in this board’s memory via LPDDR5) instead of having to either A. Have more GPUs ($$$) or B. Going all the way up to memory on the CPU which causes a big slowdown in memory access speeds. The next generation Astera “Leo 2” and Penguin’s next generation equivalent will both also be compatible with LPDDR4 Cool product. Can see the need, makes sense. I don’t know how defensible Penguin’s business here is though, I guess it’s niche enough that Astera is focused elsewhere, but I imagine that if on-prem got lucrative enough maybe Astera would come after it (many such cases across the showroom floor)
Show more
TomorrowX conference: Roboflow made an interesting observation about the differences between language and vision processing. There’s a lot of training commonality with language, whereas vision has a huge long tail problem. Every distinct AI vision application requires unique training on that vision dataset. There is no base LLM that knows all of vision, nor will there likely ever be since such a model would be ginormous. Add in that vision tasks need speed and low latency meaning on device or at least on prem models meaning smaller models and you’ve got the reason for purpose built, specific application trained models. Humans get around this by learning on the go. Ie. Continuous learning. Yet another reason why lack of continuous learning is an impediment to AI. AI will still be used and is useful, it’ll just not be as efficient from a training perspective until we have continuous learning.
Show more
We’re so early. Forget AI innings, we can’t even update legacy on prem software correctly.