[{"data":1,"prerenderedAt":346},["ShallowReactive",2],{"docsv3-nav":3,"\u002Fdocs\u002Fv3\u002Fconcepts\u002Fconcurrency":198},[4],{"title":5,"path":6,"stem":7,"children":8,"page":188},"V3","\u002Fdocs\u002Fv3","1.docs\u002Fv3",[9,13,17,21,38,87,189],{"title":10,"path":11,"stem":12},"Introduction","\u002Fdocs\u002Fv3\u002Fintroduction","1.docs\u002Fv3\u002F1.Introduction",{"title":14,"path":15,"stem":16},"Quick start","\u002Fdocs\u002Fv3\u002Fquick-start","1.docs\u002Fv3\u002F2.Quick start",{"title":18,"path":19,"stem":20},"Challenge flow","\u002Fdocs\u002Fv3\u002Fchallenge-flow","1.docs\u002Fv3\u002F3.Challenge flow",{"title":22,"path":23,"stem":24,"children":25},"Fundamentals","\u002Fdocs\u002Fv3\u002Ffundamentals","1.docs\u002Fv3\u002F4.fundamentals",[26,30,34],{"title":27,"path":28,"stem":29},"Signup protection","\u002Fdocs\u002Fv3\u002Ffundamentals\u002Fsignup-protection","1.docs\u002Fv3\u002F4.fundamentals\u002F00.Signup protection",{"title":31,"path":32,"stem":33},"Login protection","\u002Fdocs\u002Fv3\u002Ffundamentals\u002Flogin-protection","1.docs\u002Fv3\u002F4.fundamentals\u002F01.Login protection",{"title":35,"path":36,"stem":37},"Access protection","\u002Fdocs\u002Fv3\u002Ffundamentals\u002Faccess-protection","1.docs\u002Fv3\u002F4.fundamentals\u002F02.Access protection",{"title":39,"path":40,"stem":41,"children":42},"Guides","\u002Fdocs\u002Fv3\u002Fguides","1.docs\u002Fv3\u002F5.guides",[43,47,51,55,59,63,67,71,75,79,83],{"title":44,"path":45,"stem":46},"Account sharing prevention","\u002Fdocs\u002Fv3\u002Fguides\u002Faccount-sharing-prevention","1.docs\u002Fv3\u002F5.guides\u002F1.Account sharing prevention",{"title":48,"path":49,"stem":50},"Web scraping prevention","\u002Fdocs\u002Fv3\u002Fguides\u002Fweb-scraping-prevention","1.docs\u002Fv3\u002F5.guides\u002F13.Web scraping prevention",{"title":52,"path":53,"stem":54},"Ban enforcement","\u002Fdocs\u002Fv3\u002Fguides\u002Fban-enforcement","1.docs\u002Fv3\u002F5.guides\u002F14.Ban enforcement",{"title":56,"path":57,"stem":58},"Chargeback dispute","\u002Fdocs\u002Fv3\u002Fguides\u002Fchargeback-dispute","1.docs\u002Fv3\u002F5.guides\u002F15.Chargeback dispute",{"title":60,"path":61,"stem":62},"Multi-accounting prevention","\u002Fdocs\u002Fv3\u002Fguides\u002Fmulti-accounting-prevention","1.docs\u002Fv3\u002F5.guides\u002F16.Multi-accounting prevention",{"title":64,"path":65,"stem":66},"Account takeover prevention","\u002Fdocs\u002Fv3\u002Fguides\u002Faccount-takeover-prevention","1.docs\u002Fv3\u002F5.guides\u002F2.Account takeover prevention",{"title":68,"path":69,"stem":70},"Risky transaction prevention","\u002Fdocs\u002Fv3\u002Fguides\u002Frisky-transaction-prevention","1.docs\u002Fv3\u002F5.guides\u002F20.Risky transaction prevention",{"title":72,"path":73,"stem":74},"Fake account detection","\u002Fdocs\u002Fv3\u002Fguides\u002Ffake-account-detection","1.docs\u002Fv3\u002F5.guides\u002F3.Fake account detection",{"title":76,"path":77,"stem":78},"Bot detection","\u002Fdocs\u002Fv3\u002Fguides\u002Fbot-detection","1.docs\u002Fv3\u002F5.guides\u002F4.Bot detection",{"title":80,"path":81,"stem":82},"Card testing prevention","\u002Fdocs\u002Fv3\u002Fguides\u002Fcard-testing-prevention","1.docs\u002Fv3\u002F5.guides\u002F5.Card testing prevention",{"title":84,"path":85,"stem":86},"Incentive abuse prevention","\u002Fdocs\u002Fv3\u002Fguides\u002Fincentive-abuse-prevention","1.docs\u002Fv3\u002F5.guides\u002F9.Incentive abuse prevention",{"title":88,"path":89,"stem":90,"children":91,"page":188},"Concepts","\u002Fdocs\u002Fv3\u002Fconcepts","1.docs\u002Fv3\u002F6.concepts",[92,96,100,104,108,112,116,120,124,128,132,136,140,144,148,152,156,160,164,168,172,176,180,184],{"title":93,"path":94,"stem":95},"Evaluations","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fevaluations","1.docs\u002Fv3\u002F6.concepts\u002F01.evaluations",{"title":97,"path":98,"stem":99},"Actions","\u002Fdocs\u002Fv3\u002Fconcepts\u002Factions","1.docs\u002Fv3\u002F6.concepts\u002F02.actions",{"title":101,"path":102,"stem":103},"Signals","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fsignals","1.docs\u002Fv3\u002F6.concepts\u002F03.signals",{"title":105,"path":106,"stem":107},"Checks","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fchecks","1.docs\u002Fv3\u002F6.concepts\u002F04.checks",{"title":109,"path":110,"stem":111},"Risks","\u002Fdocs\u002Fv3\u002Fconcepts\u002Frisks","1.docs\u002Fv3\u002F6.concepts\u002F05.risks",{"title":113,"path":114,"stem":115},"Verdicts","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fverdicts","1.docs\u002Fv3\u002F6.concepts\u002F06.verdicts",{"title":117,"path":118,"stem":119},"Policies","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fpolicies","1.docs\u002Fv3\u002F6.concepts\u002F07.policies",{"title":121,"path":122,"stem":123},"Challenges","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fchallenges","1.docs\u002Fv3\u002F6.concepts\u002F08.challenges",{"title":125,"path":126,"stem":127},"Concurrency","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fconcurrency","1.docs\u002Fv3\u002F6.concepts\u002F09.concurrency",{"title":129,"path":130,"stem":131},"Impossible travel","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fimpossible-travel","1.docs\u002Fv3\u002F6.concepts\u002F10.impossible-travel",{"title":133,"path":134,"stem":135},"Bots","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fbots","1.docs\u002Fv3\u002F6.concepts\u002F11.bots",{"title":137,"path":138,"stem":139},"Devices","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fdevices","1.docs\u002Fv3\u002F6.concepts\u002F12.devices",{"title":141,"path":142,"stem":143},"Fingerprints","\u002Fdocs\u002Fv3\u002Fconcepts\u002Ffingerprints","1.docs\u002Fv3\u002F6.concepts\u002F13.fingerprints",{"title":145,"path":146,"stem":147},"People","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fpeople","1.docs\u002Fv3\u002F6.concepts\u002F14.people",{"title":149,"path":150,"stem":151},"Lists","\u002Fdocs\u002Fv3\u002Fconcepts\u002Flists","1.docs\u002Fv3\u002F6.concepts\u002F15.lists",{"title":153,"path":154,"stem":155},"Account takeover","\u002Fdocs\u002Fv3\u002Fconcepts\u002Faccount-takeover","1.docs\u002Fv3\u002F6.concepts\u002F16.account-takeover",{"title":157,"path":158,"stem":159},"Account sharing","\u002Fdocs\u002Fv3\u002Fconcepts\u002Faccount-sharing","1.docs\u002Fv3\u002F6.concepts\u002F17.account-sharing",{"title":161,"path":162,"stem":163},"Fake account","\u002Fdocs\u002Fv3\u002Fconcepts\u002Ffake-account","1.docs\u002Fv3\u002F6.concepts\u002F18.fake-account",{"title":165,"path":166,"stem":167},"Scraping","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fscraping","1.docs\u002Fv3\u002F6.concepts\u002F19.scraping",{"title":169,"path":170,"stem":171},"Linked accounts","\u002Fdocs\u002Fv3\u002Fconcepts\u002Flinked-accounts","1.docs\u002Fv3\u002F6.concepts\u002F20.linked-accounts",{"title":173,"path":174,"stem":175},"New IP","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fip","1.docs\u002Fv3\u002F6.concepts\u002F21.ip",{"title":177,"path":178,"stem":179},"Anonymizing network","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fanonymizing-network","1.docs\u002Fv3\u002F6.concepts\u002F22.anonymizing-network",{"title":181,"path":182,"stem":183},"Email quality","\u002Fdocs\u002Fv3\u002Fconcepts\u002Femail","1.docs\u002Fv3\u002F6.concepts\u002F23.email",{"title":185,"path":186,"stem":187},"Velocity","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fvelocity","1.docs\u002Fv3\u002F6.concepts\u002F24.velocity",false,{"title":190,"path":191,"stem":192,"children":193,"page":188},"Advanced","\u002Fdocs\u002Fv3\u002Fadvanced","1.docs\u002Fv3\u002F7.Advanced",[194],{"title":195,"path":196,"stem":197},"Proxy setup","\u002Fdocs\u002Fv3\u002Fadvanced\u002Fproxy-setup","1.docs\u002Fv3\u002F7.Advanced\u002F1.Proxy-setup",{"id":199,"title":125,"body":200,"description":339,"extension":340,"meta":341,"navigation":342,"path":126,"rawbody":343,"seo":344,"stem":127,"__hash__":345},"docsv3\u002F1.docs\u002Fv3\u002F6.concepts\u002F09.concurrency.md",{"type":201,"value":202,"toc":332},"minimark",[203,207,216,221,228,241,255,259,272,290,307,311],[204,205,125],"h1",{"id":206},"concurrency",[208,209,210,211,215],"p",{},"Concurrency is the same user accessing your service from multiple device-and-IP combinations at the same instant. It's one of the strongest ",[212,213,214],"a",{"href":158},"account sharing"," signals Rupt has: even careful sharers slip up and use the account from two places at once.",[217,218,220],"h2",{"id":219},"how-rupt-detects-it","How Rupt detects it",[208,222,223,224,227],{},"When an ",[212,225,226],{"href":94},"evaluation"," runs, Rupt checks for any other in-flight session for the same user that:",[229,230,231,235,238],"ul",{},[232,233,234],"li",{},"Is on a different IP, AND",[232,236,237],{},"Is on the same device type (mobile, tablet, computer), AND",[232,239,240],{},"Is currently active.",[208,242,243,244,248,249,251,252,254],{},"Active session presence is tracked in real time, so the detection window matches the user's actual session, not a coarse time bucket. If a second login lands while the first is still live, ",[245,246,247],"code",{},"concurrent_sessions"," flips to true on the ",[212,250,226],{"href":94}," and you'll see it surface in the ",[212,253,214],{"href":158}," risk score.",[217,256,258],{"id":257},"using-it-in-policies","Using it in policies",[208,260,261,263,264,267,268,271],{},[245,262,247],{}," is exposed directly as a ",[212,265,266],{"href":106},"check",", so you can write a ",[212,269,270],{"href":118},"policy"," condition over it:",[273,274,275],"blockquote",{},[208,276,277,278,281,282,285,286,289],{},"If ",[245,279,280],{},"event_type = access"," AND ",[245,283,284],{},"concurrent_sessions = true"," → ",[245,287,288],{},"challenge",".",[208,291,292,293,296,297,300,301,303,304,306],{},"The built-in ",[245,294,295],{},"account_sharing"," ",[212,298,299],{"href":158},"risk"," already weights ",[245,302,247],{}," heavily, so it shows up in the risk score recorded on the evaluation. To act on it in a policy today, match the ",[245,305,247],{}," check directly, which also gives you surgical control: always blocking concurrent sessions on premium tiers but ignoring them on free ones, for example.",[217,308,310],{"id":309},"pairs-well-with","Pairs well with",[229,312,313,321],{},[232,314,315,320],{},[316,317,318],"strong",{},[212,319,129],{"href":130},": physical impossibility plus simultaneous access is near-conclusive sharing.",[232,322,323,326,327,331],{},[316,324,325],{},"High device counts",": if the account has accumulated many devices over time ",[328,329,330],"em",{},"and"," shows live concurrency, the case is stronger.",{"title":333,"searchDepth":334,"depth":334,"links":335},"",2,[336,337,338],{"id":219,"depth":334,"text":220},{"id":257,"depth":334,"text":258},{"id":309,"depth":334,"text":310},"Concurrency is the same user accessing your service from multiple device-and-IP combinations at the same instant. One of the strongest account-sharing signals.","md",{},true,"---\ntitle: Concurrency\ndescription: Concurrency is the same user accessing your service from multiple device-and-IP combinations at the same instant. One of the strongest account-sharing signals.\n---\n\n# Concurrency\n\nConcurrency is the same user accessing your service from multiple device-and-IP combinations at the same instant. It's one of the strongest [account sharing](\u002Fdocs\u002Fv3\u002Fconcepts\u002Faccount-sharing) signals Rupt has: even careful sharers slip up and use the account from two places at once.\n\n## How Rupt detects it\n\nWhen an [evaluation](\u002Fdocs\u002Fv3\u002Fconcepts\u002Fevaluations) runs, Rupt checks for any other in-flight session for the same user that:\n\n- Is on a different IP, AND\n- Is on the same device type (mobile, tablet, computer), AND\n- Is currently active.\n\nActive session presence is tracked in real time, so the detection window matches the user's actual session, not a coarse time bucket. If a second login lands while the first is still live, `concurrent_sessions` flips to true on the [evaluation](\u002Fdocs\u002Fv3\u002Fconcepts\u002Fevaluations) and you'll see it surface in the [account sharing](\u002Fdocs\u002Fv3\u002Fconcepts\u002Faccount-sharing) risk score.\n\n## Using it in policies\n\n`concurrent_sessions` is exposed directly as a [check](\u002Fdocs\u002Fv3\u002Fconcepts\u002Fchecks), so you can write a [policy](\u002Fdocs\u002Fv3\u002Fconcepts\u002Fpolicies) condition over it:\n\n> If `event_type = access` AND `concurrent_sessions = true` → `challenge`.\n\nThe built-in `account_sharing` [risk](\u002Fdocs\u002Fv3\u002Fconcepts\u002Faccount-sharing) already weights `concurrent_sessions` heavily, so it shows up in the risk score recorded on the evaluation. To act on it in a policy today, match the `concurrent_sessions` check directly, which also gives you surgical control: always blocking concurrent sessions on premium tiers but ignoring them on free ones, for example.\n\n## Pairs well with\n\n- **[Impossible travel](\u002Fdocs\u002Fv3\u002Fconcepts\u002Fimpossible-travel)**: physical impossibility plus simultaneous access is near-conclusive sharing.\n- **High device counts**: if the account has accumulated many devices over time _and_ shows live concurrency, the case is stronger.\n",{"title":125,"description":339},"iP9Oa5p3S-54zObPLCI2EkpqUTT5tGVfvvSpm8Q0i3Q",1780344893439]