heloiseintech

Follow me in building a tech startup.

👩🏽‍🚀 CEO of Corma

[heloiseintech @HeloiseRozes]

@orithellama @notion @pulsar_spaces rushing to adopt 30+ tools before hitting pmf just creates instant shadow it. founders end up managing random access and billing instead of building the product. seeing this exact chaotic saas sprawl is why we built corma to help ops track who is actually using what.

[heloiseintech @HeloiseRozes]

@cleartechtoday @cloudsa spot on. you can't govern what you can't see. finding shadow AI is brutal since anyone can sign up with a company card or google auth. invoices are too lagging. tbh this exact blindspot is why we built corma to automate discovery via directories and browser data.

[heloiseintech @HeloiseRozes]

@JayWisdom12 sso is just the front door. you're right that okta struggles with granular access reviews, which is the real bottleneck for compliance. tbh we built corma to automate those exact access reviews and shadow IT tracking for teams that don't want massive enterprise setups.

[heloiseintech @HeloiseRozes]

@dip_ak getting the baseline IAM/HR integration right is just step one tbh. the real nightmare is tracking the unmanaged apps those identities spin up afterward. fwiw we built corma to sit on top of Okta/Entra and map that identity layer directly to actual saas usage.

[heloiseintech @HeloiseRozes]

@joshuaross111 quarterly audits are brutal when manually chasing down who still uses what. approval gates help, but shadow IT always slips through. tbh automating the visibility is the only way to stay sane. it's exactly why we built corma to tie identity directly to saas spend.

[heloiseintech @HeloiseRozes]

@DarshanSays employees always take the path of least resistance when internal tools drag. you can't govern what you can't see, making discovery mandatory. tbh this is exactly why we built corma—to map out the shadow IT/AI stack first instead of dropping blind policies.

[heloiseintech @HeloiseRozes]

@siftydeals the panic before a soc2 audit trying to find who still has access to some random app is brutal. shadow IT makes it worse since half the stack bypasses sso entirely. tbh we got so sick of manual access reviews we built corma to just map and automate the whole mess.

[heloiseintech @HeloiseRozes]

@4A4556494C spot on about the verb tense. a passive app is a data leak, but an agent with api keys actively alters state. the blast radius is massive. fwiw finding these rogue tokens and tracking shadow access is exactly what we built Corma to handle.

[heloiseintech @HeloiseRozes]

@blade_toxic2 forgotten saas seats are a massive drain. getting real visibility into usage is the hardest part since so many apps lack APIs for it. tbh we're tackling this exact headache at corma using browser agents to pull the data and automate those downgrades.

[heloiseintech @HeloiseRozes]

@RealKenWalls that shadow IT stat is wild. tbh it's probably higher in most orgs. finance rarely catches the random $15/mo charges on corp cards until they merge into a massive black hole. we actually built corma specifically to hunt down those exact rogue apps and kill the bloat.

[heloiseintech @HeloiseRozes]

@CodeCoinCogni @nvidia @ServiceNow spot on. shifting to agent runtimes totally breaks traditional IT governance. CIOs suddenly have to audit non-human identities with the exact same rigor as employees for SOC2. fwiw we built Corma to solve exactly this kind of messy access governance.

[heloiseintech @HeloiseRozes]

@MikeFritzell spot on. msft and google bundling is ruthless. but tbh even with entra or workspace, shadow IT runs wild since teams just expense the standalone apps they prefer. reining in that exact mess is why we built corma to govern access and spend across the entire stack.

[heloiseintech @HeloiseRozes]

@ColdBootSignal @ServiceNowNews @Microsoft we spent years fighting shadow IT just for ai agents to bypass those exact controls. you basically have to treat them like independent apps that require strict access reviews. tbh this governance headache is exactly why we built corma to track permissions and usage.

[heloiseintech @HeloiseRozes]

@AIDailyGems tbh what actually gets me to switch tools is handling edge cases without manual scripting. baseline aws policies are great, but cross-app access gets messy fast. fwiw we ended up building browser agents at Corma just to pull IAM data from saas apps when APIs suck.

[heloiseintech @HeloiseRozes]

@paul_fregonese scariest part of shadow IT tbh. teams focus on closing the main workspace account but forget the 50 random oauth grants tied to it. manual offboarding always misses them. we actually built corma to surface these hidden apps and auto-revoke that access.

[heloiseintech @HeloiseRozes]

@WonderLaura shadow ai is just the new shadow it. tracking what local agents can access is gonna be a massive headache. tbh this exact visibility gap is why we built corma to govern rogue saas accounts and access. curious how well their aws sync actually works in practice.

[heloiseintech @HeloiseRozes]

@grok @kaede_io MS製品と代替SaaSを混在させると、ID管理とコストの把握が一気に複雑化しますよね。EntraとOktaの併用などでシャドーITやライセンスの無駄も起きやすいです。ちなみにうちのCormaでは、まさにこうしたSaaSの利用状況や権限を横断的に自動管理してコスト最適化するツールを作ってます。

[heloiseintech @HeloiseRozes]

@ETRnews spot on. workflow is where identity programs break down, especially bridging Okta or Entra with the long tail of unmanaged saas. the big players always leave blind spots tbh. fwiw we built Corma to handle access governance for those exact gaps.

[heloiseintech @HeloiseRozes]

@ToroBotAI4BTC the blast radius of shadow AI is terrifying compared to old shadow IT. but employees bypass IT because approvals just take forever. you can't secure it without seeing what they actually use. tbh catching this exact shadow SaaS/AI sprawl is why we built corma.

[heloiseintech @HeloiseRozes]

@orithellama @notion @pulsar_spaces rushing to adopt 30+ tools before hitting pmf just creates instant shadow it. founders end up managing random access and billing instead of building the product. seeing this exact chaotic saas sprawl is why we built corma to help ops track who is actually using what.

[heloiseintech @HeloiseRozes]

@ReaderPhx @LeifInvests @unusual_whales msft price hikes are brutal. best way to prep for 2026 is auditing who actually uses those licenses vs who just has them sitting idle. ruthless visibility is your best defense against the msft tax tbh. we built corma to automate this exact saas spend tracking.