4,272 press releases in English indexed under saas.
TAIPEI, Oct. 5, 2026 -- The global technology supply chain is moving faster than ever. From semiconductor capacity shifts and changes in the AI chip supply chain to export controls and geopolitical developments, enterprises face a challenge that goes beyond information...
McKinney, TX Monday Oct 5, 2026 @ 8:00 PM Central — For a decade, the software playbook was simple: buy the best tool for each job and wire them together. idhubs says that era is over. Justin Mackenzie of The Building Texas Show sat down with two idhubs leaders, Founder and CEO/CTO Rojit Sorokhaibam and Chief Growth Officer Brandon Fears, to discuss why the integration model breaks under AI, what replacing the traditional software stack actually looks like, and how the company is addressing the challenges of enterprise migration. Justin: Start on a Tuesday morning. What does this problem look like for an actual business owner? Brandon: It looks like chaos they didn't choose. A business under 200 employees runs about 42 separate applications. A manager who wants to convert a prospect, send an onboarding agreement, bill a deposit and assign a kickoff task touches five of them: copy from the CRM, paste into a document tool, download, upload to e-signature, log into accounting to invoice, open a project board to assign. Five apps; five logins; one simple objective. Multiply that across a week and most of the day goes to running software instead of running the business. Rojit: And none of those systems actually agree with each other. The data in one is a slightly different version of the data in the next. For ten years the industry sold that gap as a feature and called it "best of breed." Justin: You're saying the integration model itself is the problem. Why does it break now? Rojit: AI. When AI was a chatbot, siloed data was an annoyance. Now that AI is becoming an agent that executes multi-step work, siloed data is a wall. An agent cannot intelligently complete a workflow if it has to reach across five databases that only pretend to talk through brittle webhooks. We call that context blindness. True intelligence needs one data foundation and you cannot bolt that on after the fact. Brandon: That's the line that matters: integrated means two databases that learned to talk. Native means there was only ever one. Justin: "Context blindness" is a great phrase, but let’s get concrete. What does an AI agent actually do in idhubs out of the box? Give me a real workflow, not just a buzzword. Rojit: Let’s look at customer success. In a fragmented stack, if a user posts a complaint in a community forum, a support agent has to manually read it, open the CRM, find the account, check the billing module and draft a reply. In idhubs, the AI agent natively reads the community post, instantly pulls the user's billing history from the unified invoicing module, identifies a double-charge, auto-drafts a credit memo and routes it to the manager for one-click approval, all without a human ever copying and pasting data between tabs. It executes the workflow because it has the context. Justin: So what did you build? Rojit: One natively unified operating system. Core business functions, CRM, E-commerce, community, invoicing, AI on a single shared data layer. We're not another tool for the stack. We replace the stack. Justin: You also offer a white-label community and social commerce layer. Why does that belong in an operating system? Brandon: Because the front office and the back office are the same database. An organization that deploys idhubs gets its own branded, private ecosystem: a secure internal collaboration suite for staff and a white-label community and commerce platform for its members or customers. When you build your community on a third-party social platform, you rent your audience; you don't own the data, you don't control the algorithm and you can't monetize without a cut taken off the top. Here the organization owns the relationship and because the community data lives natively beside the CRM and commerce data, a discussion can become a transaction or a support ticket without ever leaving the branded environment. It's a closed loop instead of five disconnected ones. Justin: Let me push on the architecture. If I put my CRM, financials, community and commerce in one platform, haven't I built a single honeypot? One point of failure? Rojit: That's the right question for any CIO to ask and it's why we didn't just stand up one central database and call it done. We run a permissioned, private Hyperledger Fabric network underneath the platform. Think of a public blockchain as a town square where everyone sees every transaction; this is the opposite. Fabric uses channels and private data collections, so sensitive records are visible only to the nodes, the users or departments, that are cryptographically authorized to see them. The organization gets the decentralization and immutability of distributed ledger architecture entirely inside its own walls, which neutralizes the single-point-of-failure risk that comes with traditional monolithic software. Justin: But running a private blockchain network sounds incredibly resource-intensive. Doesn't that introduce latency and bloat the infrastructure costs for a 50-person company? Rojit: That’s a common misconception based on public chains like Bitcoin. Hyperledger Fabric is built for enterprise performance. We don't store heavy payloads on the ledger itself; we use off-chain storage for large files and media, while the ledger only cryptographically anchors the state changes and audit trails. It runs asynchronously in the background. It doesn't slow down the user interface or query speeds, but it gives you military-grade auditability and data sovereignty without the enterprise infrastructure bill. Justin: Who's behind this and how big is the opportunity? Rojit: We're a live, revenue-generating platform, not a stealth lab. I'm a three-time exited CTO who has scaled 150-plus-person engineering teams. Brandon has launched more than $2 billion in products. Sav, our COO, is a 30-year operations leader. Our advisory board includes Grant Johnson, former CEO of a NASDAQ-listed company and Craig Kaufman of Kaufman Bros. Brandon: On the market: our total addressable market is roughly $158 billion. We've acquired more than 50,000 registered users organically, with no paid marketing spend. Justin: Let’s drill into your pricing model. You’ve mentioned a "flat, predictable annual rate" that lands well under fragmented tools. But a 5-person company and a 150-person company have vastly different needs. How does your pricing scale without becoming a new "idhubs tax" as they grow? Brandon: We specifically killed the per-seat pricing model because it punishes companies for scaling their teams. Our pricing scales based on organizational capacity and active transactional volume, not headcount. You don't get hit with hidden integration fees, per-API-call charges, or forced module upgrades. It’s a flat, predictable rate for the core OS, with transparent, tiered capacity bumps. You know exactly what your software bill will be in Q4, regardless of whether you hired five people or fifty. Justin: What do the skeptics say? Best-of-breed purists love their point solutions. Brandon: I hear it constantly and it sounds great until you price it. A five-person company ends up paying for a CRM, an automation connector, a quoting tool, an email platform and an accounting suite, spends tens of thousands a year and its data still doesn't agree across systems. The "flexibility" is a fragmentation tax in a nicer outfit. The opposite of a bad stack isn't a better stack; it's one platform, one login, one source of truth. Justin: But purists will counter: "Sure, it's unified, but is the invoicing as deep as Stripe? Is the CRM as robust as Salesforce?" How do you avoid the "good enough" trap where you hit a ceiling as the client scales? Rojit: We aren't building shallow wrappers. We are building deep, API-first modules. For example, our financials handle complex multi-currency and automated tax compliance natively because we built it for global commerce from day one. But if a company has a hyper-niche, proprietary workflow, we don't force them to rip and replace the whole OS. Because we have a unified data layer, they can build custom extensions and micro-apps on top of idhubs. They get the depth of a custom build with the unified context of an OS. Justin: Even if it’s deep, the switching cost is the real killer. Migrating data, workflows and user habits from entrenched systems is a nightmare. How do you actually get a company to switch without paralyzing their operations for six months? Brandon: We knew migration was the graveyard of great software, so we engineered it out of the equation. We built automated migration pipelines specifically for the major incumbents, HubSpot, QuickBooks, Salesforce, Slack. We don't do "big bang" cutovers. We run parallel environments and our onboarding team maps the data schema automatically. We measure time-to-value in days, not quarters. The user interface is designed to feel familiar, so the human habit-change is minimal. Justin: Finally, you're not the only one claiming "all-in-one." Zoho, Odoo, HubSpot, they all have unified suites and are aggressively adding AI. Why does idhubs win against them? Rojit: Because legacy suites were built as separate apps glued together later. Their data layers are still fragmented underneath; they are still fighting the integration tax internally. We are natively unified from the ground up on a single data layer. Furthermore, our Hyperledger security model is enterprise-grade out of the box, which legacy SMB suites completely lack. They are a suite of tools trying to act like an OS. We are a single, secure operating system. The skeptics are fighting the last war. In the AI era, context is the whole game. Justin: Last question. If this model wins, what's the ripple effect? Rojit: Software stops being a daily operational burden and becomes a silent partner. Eliminate the integration tax, secure the data natively and human capital goes back to strategy instead of reconciliation. For member organizations it turns a siloed directory into a connected economic ecosystem. Brandon: Owners didn't choose complexity; the market handed it to them one app at a time. Every vendor promises the next app will fix it. But the next app can't fix it, because the app was the problem. The fix was never one more tool or one more integration. It was always one secure, unified platform. That's what we built and that's why the shift is inevitable. Rojit Sorokhaibam is Founder and CEO/CTO of idhubs. Brandon Fears is Chief Growth Officer. idhubs is headquartered in McKinney, Texas.
Every software build is assembled from open source packages, base images, and libraries, with your code on top. When one of those components is missing or has drifted, the build fails. At agent speed, those failures multiply, and no team can clear them as manual exceptions. Project-by-project registry sprawl makes it worse because retention rules, storage limits, and publish access all live separately inside each project. Project-level design works when a person sets up each registry by hand, but breaks down when agents are running continuously across hundreds of projects. At GitLab Transcend today, we announced GitLab Artifact Central: one organization-level registry that replaces hundreds of project-level ones, so every pull or publish by a human or an agent runs through the same governed door, enabling platform teams to assemble the right software the first time. Here is more on why we developed Artifact Central, and how it can help your team. Set policy once, enforce everywhere In GitLab, retention rules, storage limits, and who can publish all live inside each project’s free package and container registry, configured on its own. GitLab Artifact Central moves that job up one level. Teams assign retention rules, quota settings, and access policies once at the organization level, instead of recreating them in every project underneath it. Every repository is closed by default: Being a member of the organization is the gate, not the grant. Organization membership alone doesn't unlock a single repository until a role grants it. We’ve built four roles specifically for artifacts: Admin, Manager, Contributor, and Viewer. These roles are kept separate from GitLab's existing project roles, so granting someone access to a repository never touches their privileges anywhere else. One URL for publishing, proxying, or both Instead of navigating an internal wiki page explaining what is where, developers point to one URL for everything. GitLab Artifact Central does this through three repository types: Hosted — The private packages and images your teams build and publish. Remote — A proxy in front of an external source, like Docker Hub or Maven Central, with the connection tested before anything depends on it. Virtual — A single endpoint that brings hosted and remote repositories together. GitLab checks the hosted repository first, then falls back to the remote source. The first external pull is cached, so subsequent pulls come directly from GitLab without another trip to the internet. Virtual repositories matter most for teams comparing GitLab with other artifact management solutions. They give developers the familiar single-endpoint experience without requiring them to think about where an artifact lives. Whether it was built internally or pulled from an external registry, developers request it the same way. During the beta period, Artifact Central supports Maven, npm, Docker, and OCI, with more formats to follow. Trace anything back, automatically Here's the part that's hard to replicate outside GitLab. Every artifact that publishes through GitLab Artifact Central carries its build provenance automatically: which pipeline built it, which branch and commit it came from, who triggered the job. Since it is the same platform that ran the build, the registry already knows. Authentication works the same way. Publishing and pulling use CI_JOB_TOKEN, the identity your pipelines already have, for people and agents alike. An agent publishing or pulling through CI pipelines uses that exact same job token, not a bolted-on service account with separate permissions to maintain. With a standalone registry, tracing an artifact back to its source means separately correlating IDs across your CI system and your registry – using a script someone owns and maintains. With Artifact Central, the pipeline, branch, commit, and job are already attached to the artifact itself. Answer 'what did we publish?' in seconds Artifact Central lives in the same platform as your code, merge requests, and pipelines, so artifacts published from CI carry their build provenance: the pipeline that built them, the commit, and who published them. Next, we plan to connect that across your organization through GitLab Orbit, so "which of my running services are affected by this vulnerability?" becomes one question with one answer, instead of a manual search across four or five tools. Pair Artifact Central with Dependency Firewall GitLab Dependency Firewall, a separate GitLab product now in early access for Premium and Ultimate customers, works out of the box with Artifact Central. With Dependency Firewall, you can stop risky packages before they ever reach a build. You add its check to each pipeline using the glab CLI, so coverage is pipeline by pipeline, no matter which package manager your teams use. Next, we plan to enable tighter integration between the two capabilities, so that one policy for your whole organization blocks risky packages by vulnerability, license, or package age the moment they're pulled. Two benefits of the same registry Here's what that looks like from two different desks: a developer shipping code, and the platform team making sure the whole thing holds together. A developer publishing from CI. Your pipeline publishes a Maven artifact using the job token it already has without any new secrets to manage. If that same developer needs an internal package alongside something from Maven Central, they point at one virtual repo URL and let GitLab Artifact Central sort out where each one actually lives. A platform team setting policy once. Instead of configuring rules across 100s of separate projects, an admin sets storage quotas and repository access rules at the organization level, one time — and every repository underneath inherits it. When someone asks how much the company is storing, and where, there's one dashboard with the answer. Migrating your artifacts Most companies aren't starting from zero, and switching cold from an existing registry isn't realistic. With GitLab Artifact Central, you can add your existing repos as remotes behind a virtual repo, so developers point at one URL and artifacts move over only when a build actually asks for one. There is no need for bulk copies, weekend migration windows, or moving petabytes of data across your network. Your old registry remains the system of record. When you're ready, you convert that remote to a hosted repo on Artifact Central. Your migration is safer and gradual. Try Artifact Central, free in beta GitLab Artifact Central is available today in beta for GitLab.com, with availability on GitLab Self-Managed planned for later this month. There's no billing during the beta, and nothing to purchase. We're tracking usage to shape pricing ahead of general availability, and we'll share details then. Help us continue to build GitLab Artifact Central None of this would be where it is without our design partners, who've been running Artifact Central with real workflows for weeks. Their feedback already shaped what's shipping today, and your feedback will shape what comes next. No invitation is required to participate in the beta of Artifact Central, just sign up on our website and a member of our team will be in touch to help enable it for your account. If you don’t have a GitLab account yet, you can also sign up for the beta, and a member of our team will reach out. We can't wait to see what you build. Watch the replay of our Transcend event to see demos of new platform capabilities and explore what it takes to carry the speed of agentic AI across the full software lifecycle.
At Transcend, we made over a dozen announcements across all four layers of our architecture for agentic software engineering: agent orchestration, data and context, DevOps workflows, and governance and security. Watch the replay, or read on for what shipped and how to turn on the new capabilities. At a glance What we launchedRelease statusWhat it does Goal-driven flows (/goal)GA this monthCarry a change through review, tests, scans, and approvals without waiting between stages of the software lifecycle. Custom FlowsGAChain agents together to match the process your teams already follow for software delivery. GitLab for SlackGA this monthStart an agentic flow from the channels where your teams already work. MCP ServerGA this monthSecurely connect AI tools and applications into GitLab workflows under the same policy. Open weight modelsGAGet comparable performance on lower-cost workloads with GitLab-hosted GLM 5.3, Kimi K3, and MiniMax 3 models. GitLab OrbitGA next monthGive your agents the right knowledge requiring 45x fewer retries with a context graph of your software lifecycle. Duo Agent Platform Impact AnalyticsEarly accessMeasure the cost and impact of your AI investment, by team, task, and model. Credit and usage controlsGASet caps at the subscription, group, and user level and get alerts on AI spend. GitLab Artifact CentralBetaGive every package and container one governed home, next to source and CI. GitLab Dependency FirewallEarly accessSet rules that block, quarantine, or warn on risky packages before they reach your build. GitLab Secrets ManagerGA this monthScope build-time secrets to the job and revoke them with one click. GitLab Security StandardAvailable todayHarden your software factory in five stages and let your agents earn autonomy. New flows with Claude Mythos 5 and 5.1GA next monthFind and remediate vulnerabilities on GitLab Duo Agent Platform with new security flows. Agent orchestration across the software lifecycle Today, each step in your agentic workflow still waits for a person to approve it before the next one starts. Goal-driven flows take a stated objective and run it end to end, through review, tests, security scans, and approvals from the Duo CLI, headless mode, or Agentic Chat. Custom Flows let you chain agents together to match the process your team already follows. GitLab for Slack starts a flow from the channel where the conversation is already happening. The MCP Server enables external AI applications and coding agents to securely access your GitLab instance under the same policy your own agents follow. GitLab-hosted open-weight models, including GLM 5.3, Kimi K3, and MiniMax 3, give you a lower-cost option when a workload doesn't need a frontier model. At similar task-completion rates, some open weight pairings deliver up to 8x more model calls per GitLab Credit than their frontier counterparts. Data and context to power human and agent reasoning Every agent task starts by re-deriving the same context, which drives up retries and token use. And without coherent visibility into AI costs and ROI, there's no way to tell whether your investment is paying off. GitLab Orbit, the context graph of your entire software lifecycle increases agent accuracy with up to 45x fewer retries, effectively reducing cost for agentic workflows with up to 4.5x fewer token use. During its beta period, Orbit has been used by more than 3,500 organizations, running over 280,000 queries. Duo Agent Platform Impact Analytics shows the cost and impact of your AI investment by team, task, and model. Credit and usage controls let you set caps at the subscription, group, or user level, with alerts at 50%, 80%, and 100% of spend, and an automatic pause once you hit the cap you set. DevOps infrastructure at agent scale Most of what ships isn't code your team wrote, it's assembled from open source packages, base images, and libraries pulled in from everywhere. When every team runs its own registry, there's no single place to confirm what you actually published or shipped. Back in June, during Transcend London, we introduced our next-gen source code management solution helping you achieve machine scale with your coding agents. The next machine-scale problem goes to the step after code, when you’re creating a build. GitLab Artifact Central replaces a separate registry per team with one place to publish and pull from, built next to your source code and CI pipelines. It publishes and pulls Maven, npm, and Docker, and OCI packages directly from CI pipelines, with PyPI and NuGet coming at GA. Artifact Central uses the same identity and permissions as your source code, with virtual repos, native CI/CD authentication, and full build provenance. Early results show roughly 50% lower total cost of ownership compared to alternative tooling. Governance and security with centralized enforcement Agents pull in package components to your build at machine speed, making it impossible to manually secure what you ship. When that gap exists, you risk shipping security vulnerabilities into production rather than catching them before they impact customers, and you have to answer for it. GitLab Dependency Firewall, now in early access, sets rules on package age, vulnerability severity, malicious package detection, and license compliance, with actions to block, quarantine, or warn, enforced on the registries you already use. It works directly with GitLab Artifact Central, and is compatible with JFrog Artifactory and Sonatype Nexus Repository. With a greater number of builds, another risk emerges: agents inheriting build-time secrets from local dev environments that nobody secured, and using them across CI pipelines. GitLab Secrets Manager gives each build-time secret one home, scoped to the job that needs it, with one-click revocation for a leaked credential and up to 50% savings compared to hosting a separate vault. The same AI models that let agents write and ship code at machine speed also make existing weaknesses faster and cheaper to discover, connect, and exploit. The GitLab Security Standard lays out five stages for assessing and hardening your agentic software development: authorizing every actor's access, isolating workspaces and their inputs, verifying the checks that judge the work, releasing exactly what was verified, and responding fast when something looks wrong, all built on a foundation of policy, audit, and ownership. Read the full standard for the complete breakdown. Coming soon, Anthropic’s Claude Mythos 5 and 5.1 will power new GitLab Duo Agent Platform security flows, helping organizations with approved environments find and fix vulnerabilities faster than attackers can discover and exploit them. How to buy with GitLab Flex Agentic software engineering makes headcount, credit burn, and new capabilities hard to predict six months out. GitLab Flex is one annual commitment that covers new GitLab capabilities as they ship, without re-procurement. It lets teams reshape seat and AI spend via GitLab Credits on a monthly basis as their needs change. Where to start Turn on GitLab Duo Agent Platform: Existing customers start today with credits already in their subscription, and every new GitLab trial includes 30-day access. To increase the efficiency of your agents, turn on GitLab Orbit beta for GitLab.com. Adopt the GitLab Security Standard: GitLab Ultimate is available as a free trial. A Secrets Manager trial is available to Ultimate and Premium customers. GitLab Artifact Central is open in beta, and you can request early access to Dependency Firewall. Get more from every dollar with GitLab Flex: One annual commitment for new GitLab innovations without re-procurement - with the ability to reshape your spend for seats and GitLab Credits month to month. If you're migrating from GitHub, do it on your own terms with dedicated migration tools, custom migration services, and an exclusive offer to get one year of GitLab free when signing up for a three-year contract. And if you're ready to start building, join "Life after code: the path to production at the speed of imagination," our three-week hackathon in partnership with Anthropic and Google Cloud. Wherever you start, you're choosing the same destination: the foundation for a governed software factory where agents accelerate the work and every change stays trusted. We can’t wait to see what you build next.
NEW YORK, Oct. 5, 2026 -- BC Partners Credit, the credit arm of BC Partners, today announced an initial committed investment in LIV Golf by funds advised on its platform. This investment is the first part of a targeted $300 million in cumulative financing to help LIV Golf...
MARLBOROUGH, Mass., Oct. 05, 2026 -- IPG Photonics today announced that from October 6th though October 8th, 2026, IPG Defense will participate in Land Forces 2026 in Perth, Australia to showcase CROSSBOW™ High-Energy Laser (HEL) Systems. This key industry event provides a platform to forge strategic alliances and collaborate to shape the future of the global aerospace and defense market.
Las Vegas Security Leader Enhances User Experience with Cutting-Edge Digital Platform Las Vegas Security Leader Enhances User Experience with Cutting-Edge Digital Platform
TEAM Anywhere/SAN FRANCISCO, October 05, 2026--Atlassian Corporation (NASDAQ: TEAM), a leading provider of AI collaboration and productivity software for teams, today announced that it will release financial results for its first quarter of fiscal year 2027 ended September 30, 2026 after market close on Thursday, November 5, 2026. Atlassian will host a conference call to discuss the financial results at 2:00 P.M. Pacific Time.
Chicago, Illinois--(October 5, 2026) - SlabOS, a countertop fabrication and shop-management platform, has published the SlabOS Knowledge Library, a public resource documenting the more than 150 capabilities that connect the quote-to-install workflow in countertop and stone fabrication businesses. The library includes 43 capability guides, 39 feature deep dives, four detailed reports and a connected fabrication workflow map covering drawing, nesting, inventory, customer...
New Platform Offers Free Resources and Guides for Informed Borrowing Decisions Across the United States New Platform Offers Free Resources and Guides for Informed Borrowing Decisions Across the United States
NEW YORK, October 05, 2026--ANV Group Holdings Ltd. ("ANV"), a global insurance intermediary platform, today announced it has completed its acquisition of Assured Underwriting Group Limited ("AUG"), a specialist MGA providing insurance-backed financial protection products to tour operators and the travel sector across the United Kingdom and Europe. The transaction has received all necessary regulatory approvals.
The post How Power Platform helps businesses build AI into existing apps appeared first on Source.