Insights
Practical writing on software architecture, SaaS products, AI automation, legacy modernisation, and the business of building reliable systems.
Curated links from external sources — not 360Softy original articles.
Cloudflare has updated Logpush datasets: Updated fields in existing datasets Gateway DNS (added): AppliedMaxTTL and UpstreamRecordTTLs. Gateway HTTP (added): Warnings. HTTP requests (added): CacheLockWaitedMs. For the complete field definitions for each dataset, refer to Logpush datasets.
When you connect a data source to your AI Search instance, AI Search runs sync jobs to keep your index up to date with your content. You can now manage those jobs directly from Wrangler. For example, you can trigger a sync job from your CI/CD or automated pipelines with the jobs create command so your index refreshes when you push a change: wrangler ai-search jobs create my-instance This creates an asynchronous sync job that checks for changes in your data source, and sends new, modified,
You can now add hostname routes to a Cloudflare Mesh node, in addition to CIDR routes. Client device Requests wiki.internal.local DNS query ↓ Cloudflare Gateway Returns a token IP, then rewrites the destination to the real private IP. 100.80.0.0/16 Hostname route ↓ Mesh node Forwards traffic to the host on the local network ↓ Private host wiki.internal.local · 10.0.0.50 Instead of managing IP ranges, you can attract traffi
Wrangler CLI now supports auth profiles: named logins that you scope to specific Cloudflare accounts and switch between automatically, based on the directory you are working in. A profile is a named OAuth login bound to a directory. Commands run in that directory, and its subdirectories, use the matching account — so you can move between accounts without re-running wrangler login. Use profiles to keep a separate login for each client when working at an agency, or to separate staging and producti
Gigamon COO Gareth Maclachlan explains how the Gigamon–Elastic partnership delivers deep observability — enabling faster threat detection, Zero Trust enforcement, and AI traffic governance.
Your AI agent confidently tells a user that the company's parental leave policy is 12 weeks. It's been 16 for the past year. The old HR handbook, the updated one, and the Slack announcement that changed it are all sitting in the retrieval index. The a...
now supports .Vercel AI Gatewayrouting rules Routing rules are firewall-style rules that control which models your team can use, applied at the gateway level instead of in your application code. When a model goes down or gets retired, you usually have to ship a code change to move off it. With routing rules, you push one rule and every request reroutes instantly. There are two types: Rules apply to every request made with your team's AI Gateway credentials. You manage them with the .Vercel CLI C
Work with 360Softy
Book a free consultation and we will tell you honestly whether we can help.
