VELO Strangle Strategy
VELO (Velo3D, Inc.), in the Technology sector, (Computer Hardware industry), listed on NASDAQ.
Velo3D, Inc. produces and sells metal additive three dimensional printers in the Americas, Europe, and internationally. The company's printers enable the production of components for space rockets, jet engines, fuel delivery systems, and other metal parts, which it sells or leases to customers for use in their businesses. It also offers Flow, a proprietary software platform, which scans part designs for geometrical features; and Sapphire, Sapphire 1MZ, Sapphire XC, and Sapphire XC 1MZ printers. In addition, the company provides Assure, a quality control software platform that includes process metrologies; Flow Developer, a new version of print preparation software that turns traditional design files into print files; and Intelligent Fusion, an underlying manufacturing process that unifies and manages the information flow, sensor data, and the advanced printing technology for precision control of the entire print. Further, it offers Rapid Production Solutions to build resilient supply chains for production parts in different industries; and provides support services. The company serves small- and medium-sized enterprises to Fortune 500 companies in the space, aviation, defense, automotive, energy, and industrial markets.
VELO (Velo3D, Inc.) trades in the Technology sector, specifically Computer Hardware, with a market capitalization of approximately $439.6M, a beta of 2.27 versus the broader market, a 52-week range of 2.81-23.84, average daily share volume of 2.8M, a public-listing history dating back to 2021, approximately 105 full-time employees. These structural characteristics shape how VELO stock options price implied volatility around earnings windows, capital events, and macro-driven sector rotations.
A beta of 2.27 indicates VELO has historically moved more than the broader market, amplifying both the directional payoff and the realized volatility relative to an index-equivalent position.
What is a strangle on VELO?
A long strangle buys an OTM call and an OTM put at offset strikes, cheaper than a straddle but requiring a larger underlying move to profit since both wings start out-of-the-money.
Current VELO snapshot
As of May 15, 2026, spot at $18.75, ATM IV 136.70%, expected move 39.19%. The strangle on VELO below is built from the same end-of-day chain, with strikes snapped to listed contracts and premiums pulled from the bid/ask midpoint at a 34-day expiry.
Why this strangle structure on VELO specifically: IV rank is unavailable in the current snapshot, so regime-based timing for VELO is inferred from ATM IV at 136.70% alone, with a market-implied 1-standard-deviation move of approximately 39.19% (roughly $7.35 on the underlying). The 34-day window matched to the front-month expiry keeps theta exposure bounded while still capturing the post-snapshot move; longer-dated VELO expiries trade a higher absolute premium for lower per-day decay. Position sizing on VELO should anchor to the underlying notional of $18.75 per share and to the trader's directional view on VELO stock.
VELO strangle setup
The VELO strangle below is built from the end-of-day chain, with each option leg priced at the bid/ask midpoint of its listed strike. With VELO near $18.75, the first option leg uses a $19.69 strike; additional legs (when the strategy has them) anchor to spot-relative offsets. Premiums come from the bid/ask midpoint on the listed VELO chain at a 34-day expiry; the cross-strike IV skew is reflected directly in the per-leg values rather than approximated. Quantity sizing assumes one contract per option leg (or 100 VELO shares for the stock leg in covered calls and collars).
| Action | Type | Strike / Basis | Premium (est) |
|---|---|---|---|
| Buy 1 | Call | $19.69 | N/A |
| Buy 1 | Put | $17.81 | N/A |
VELO strangle risk and reward
- Net Premium / Debit
- N/A
- Max Profit (per contract)
- Unbounded
- Max Loss (per contract)
- Unbounded
- Breakeven(s)
- None on modeled curve
- Risk / Reward Ratio
- N/A
Upside max profit is unbounded; downside max profit is bounded at the put strike minus the combined debit (reached at zero). Max loss equals the combined debit times 100 (reached anywhere between the two OTM strikes). Two breakevens at call-strike plus debit and put-strike minus debit.
VELO strangle payoff curve
Modeled P&L at expiration across a range of underlying prices for the strangle on VELO. Each row is one sampled price point from the computed payoff curve; the full curve uses 200 price points internally before being summarized into 10 rows here.
When traders use strangle on VELO
Strangles on VELO are the cheaper cousin of the straddle - traders use them when they want a large directional move but are willing to give up the inner-strike sensitivity in exchange for a lower up-front debit on the VELO chain.
VELO thesis for this strangle
The market-implied 1-standard-deviation range for VELO extends from approximately $11.40 on the downside to $26.10 on the upside. A VELO long strangle is the OTM cousin of the straddle: lower up-front cost but the underlying has to travel further past either OTM strike before the position turns profitable at expiration. As a Technology name, VELO options can move on sector-level news flow (peer earnings, regulatory updates, industry-specific macro data) in addition to VELO-specific events.
VELO strangle positions are structurally neutral / high-volatility (long premium, OTM); the modeled P&L assumes European-style exercise at expiration and ignores early assignment, transaction costs, dividends paid before expiry on the stock leg (when present), and the bid-ask spread on the listed chain. VELO positions also carry Technology sector concentration risk; news flow inside the sector (peer earnings, regulatory shifts, supply-chain headlines) can move VELO alongside the broader basket even when VELO-specific fundamentals are unchanged. Always rebuild the position from current VELO chain quotes before placing a trade.
Frequently asked questions
- What is a strangle on VELO?
- A strangle on VELO is the strangle strategy applied to VELO (stock). The strategy is structurally neutral / high-volatility (long premium, OTM): A long strangle buys an OTM call and an OTM put at offset strikes, cheaper than a straddle but requiring a larger underlying move to profit since both wings start out-of-the-money. With VELO stock trading near $18.75, the strikes shown on this page are snapped to the nearest listed VELO chain strike and the premiums come straight from the end-of-day bid/ask midpoint.
- How are VELO strangle max profit and max loss calculated?
- Upside max profit is unbounded; downside max profit is bounded at the put strike minus the combined debit (reached at zero). Max loss equals the combined debit times 100 (reached anywhere between the two OTM strikes). Two breakevens at call-strike plus debit and put-strike minus debit. For the VELO strangle priced from the end-of-day chain at a 30-day expiry (ATM IV 136.70%), the computed maximum profit is unbounded per contract and the computed maximum loss is unbounded per contract. Live intraday quotes will differ as the chain moves through the trading session.
- What is the breakeven for a VELO strangle?
- The breakeven for the VELO strangle priced on this page is no defined breakeven on the modeled curve at expiration, derived from end-of-day chain premiums. Breakeven is the underlying price at which the strategy's P&L crosses zero ignoring transaction costs and assignment risk. The current VELO market-implied 1-standard-deviation expected move is approximately 39.19%; if the move sits well outside the breakeven distance, the structure's risk-reward becomes correspondingly tighter.
- When should you consider a strangle on VELO?
- Strangles on VELO are the cheaper cousin of the straddle - traders use them when they want a large directional move but are willing to give up the inner-strike sensitivity in exchange for a lower up-front debit on the VELO chain.
- How does current VELO implied volatility affect this strangle?
- Current VELO ATM IV is 136.70%; IV rank context is unavailable in the current snapshot.