IT residence permit — narrower fit than most foreign IT founders expect.

What you get#

A Georgian residence permit grounded by qualification under Article 15(l) of the residence permit framework — specific NACE/ISCO code-defined IT activities. The IT residence permit serves a narrower configuration than its name suggests: most foreign IT founders, contractors, and operators we work with don't actually fit Article 15(l)'s framework, even when their work is genuinely IT-related. The page's primary value is honest assessment of whether IT residence is the right pathway versus the alternatives — and for most readers, the answer is "a different pathway fits better."

The structure has four other clean properties:

Article 15(l) is genuinely narrow. The Article 15(l) qualification applies to specific IT activities defined by NACE (Statistical Classification of Economic Activities) and ISCO (International Standard Classification of Occupations) codes. The codes capture specific roles and activities — software development for specific industries, IT specialist roles in specific configurations — rather than broad "IT-related work." Foreign IT founders running their own LLCs serving foreign clients typically fit work residence (IE-grounded) or investment residence (LLC-grounded) frameworks better, since their qualification doesn't ground in the specific Article 15(l) code framework.

Honest deflection is the page's job. This page exists to serve the minority of readers who genuinely fit Article 15(l) — and to honestly redirect the majority who don't. Most foreign IT readers we encounter fit one of three other pathways: Work Residence (IE+SBS configuration for foreign-client IT work, the most common fit), Investment Residence (LLC-scale operations with substance, often combined with Virtual Zone LLC or International Company status), or Property Residence (when the IT founder's Georgian commitment is property-focused). The Residency Scoping walks through which pathway actually fits.

Standard 10-year track to permanent residence. Like property and work residence, IT residence counts toward the standard 10-year continuous lawful residence requirement for permanent residence application — not the 5-year accelerated track that the Investment Permit specifically grants. For foreign IT founders pursuing the citizenship long-horizon goal, the 5-year acceleration available via Investment residence is meaningful. IT residence at Article 15(l) doesn't carry that acceleration.

Initial application physical, renewals via PoA. Like all residence permit categories, the IT residence permit's initial application requires physical presence at the SDA Public Service Hall for biometric capture and first card collection. Annual renewals run remote-via-PoA from year 1 onward.

The combined effect: a residence permit pathway available for foreign IT specialists who genuinely fit Article 15(l)'s NACE/ISCO code framework — and a clear deflection point for the more common case where a different pathway fits the actual configuration better.

What we do#

The first 30 minutes of any IT residence conversation is determining whether Article 15(l) actually fits — and most often, it doesn't.

Step 1 — Residency Scoping against Article 15(l). We map your specific IT work configuration against the NACE/ISCO code framework that grounds Article 15(l). Specific software development roles, specific IT specialist activities, specific configurations the regulation captures. Configuration that fits within these codes qualifies; configuration that's broadly "IT-related" but doesn't match the specific codes doesn't qualify regardless of how IT-heavy the actual work is.

Step 2 — Alternative pathway assessment when 15(l) doesn't fit. For most foreign IT readers we work with, the Residency Scoping concludes that Work Residence (IE+SBS for foreign-client IT work), Investment Residence (LLC-scale Georgian operations), or Property Residence (property-focused commitment) fits the configuration better than IT residence. We map your situation against the better-fitting pathway and recommend the appropriate engagement.

Step 3 (only if Article 15(l) fits) — IT residence permit application. For the minority of cases where Article 15(l) genuinely fits, we file the IT residence permit application at the SDA. The application file documents the qualifying NACE/ISCO code framework alignment. We prepare the documentation pack and accompany you through the process.

Step 4 (only if 15(l) fits) — Initial physical visit + ongoing renewals. The IT residence permit application requires your physical presence at the SDA Public Service Hall for biometric capture, like all residence permit categories. Annual renewals from year 1 onward run remote-via-PoA — we handle the renewal documentation, demonstrate continued Article 15(l) qualification, and collect the renewal card on your behalf.

What's included#

Residency Scoping (the standalone engagement, the dominant outcome for most readers):

• Mapping your specific IT work configuration against Article 15(l) NACE/ISCO code framework
• Identifying whether 15(l) qualifies your specific configuration or whether a different pathway fits better
• Written recommendation of the actually-correct residency pathway for your situation
• Brief on what to keep on file regarding pathway choice

IT Residence Application (when Article 15(l) genuinely fits):

• Full IT residence permit application file preparation under Article 15(l)
• Documentation of NACE/ISCO code framework alignment
• Power of Attorney drafting and notarisation coordination
• Coordination of the initial Georgia visit (timing, scheduling, accompanying you through SDA interactions)
• First card collection (during initial visit if processing speed allows, or via separate trip otherwise)
• Annual renewal handling via Power of Attorney from year 1 onward

What you'll need to qualify#

Two things, both genuinely strict.

Specific NACE/ISCO code framework alignment. Your IT work must match the specific codes Article 15(l) captures — not "IT work" generally but specific code-defined activities. The qualifying code framework is narrower than most foreign IT readers expect; broad descriptions like "software developer" or "IT consultant" don't automatically qualify, the specific code-mapped activity has to fit. We walk through the code mapping in the Residency Scoping.

Demonstrable IT specialist activity. The qualifying configuration requires demonstrable specialist activity, not generic IT-related work. Documented evidence of the specific NACE/ISCO code-aligned work, supporting documentation of professional qualifications matching the regulation, and operational evidence of the specialist activity. The SDA's review focuses on whether the specialist activity is genuine and code-aligned, not on whether the applicant identifies as "IT."

We work through both in the Residency Scoping and confirm whether Article 15(l) applies before any application engagement.

When IT residence is the right pathway (and when it isn't)#

Choose IT residence when all of these apply:

• Your IT work matches specific NACE/ISCO codes captured by Article 15(l) (not just "IT-related" broadly)
• Your specialist activity is documentable in the framework the regulation expects
• Your professional qualifications and supporting evidence align with the specific code framework
• Other pathways don't fit your configuration cleanly (most IT founders fit work or investment residence better despite the IT framing)

Choose a different pathway when these apply (the more common case):

Work Residence — for the typical foreign-client IT freelancer. Foreign IT contractors, freelancers, and consultants serving foreign clients through a Georgian Individual Entrepreneur with Small Business Status fit work residence cleanly. The IE+SBS configuration grounds the residence permit under Article 15(a) — operationally simpler than Article 15(l), with the 1% turnover tax benefit, and grounds residence regardless of specific IT specialty within the broader "foreign-client business activity" framing.

Investment Residence — for foreign IT founders running LLC-scale operations. Foreign IT founders with substantial Georgian LLC operations (especially Virtual Zone LLCs or International Company status holdings) ground residence under the Investment pathway, with the 5-year accelerated permanent residence track. This is the most common fit for IT founders running software companies with operational scale.

Property Residence — for property-focused commitments. IT founders who buy Georgian property at USD 150,000+ as their primary commitment ground residence under property — operationally simpler than IT residence, with no minimum stay requirement.

The Residency Scoping confirms which pathway actually fits. Sometimes the "obvious" choice (an IT founder choosing IT residence) isn't the right answer because the configuration fits a different pathway better.

Why Happy Georgia#

Independent advisory. No tied immigration or IT-services businesses. We assess whether IT residence fits your configuration honestly — and for most readers, the recommendation is a different pathway despite the "IT" label appeal. Independent advisory means we don't push you toward an engagement that won't satisfy the SDA.

Foreign clients only. Our entire practice is foreigners setting up in Georgia. We've worked through the IT residence Residency Scoping for many foreign IT founders — most concluding with Work Residence (the IE+SBS configuration) or Investment Residence (the LLC-scale configuration) as the better-fitting pathway, with a small minority where Article 15(l) genuinely captures the configuration.

Fixed pricing, no tourist tax. Residency Scoping on request; IT residence application engagement on request when Article 15(l) genuinely fits. We quote in EUR, we honor the quote, no surprises later.

Trusted by clients across Western Europe, Israel, the UK, Singapore, and beyond.

Frequently asked questions#

Why is the IT residence permit so narrow when so many founders work in IT?#

Article 15(l)'s framework operates on specific NACE/ISCO codes that capture defined IT specialist roles and activities — not the broader "founder of an IT company" or "IT freelancer" configurations that most foreign IT readers we work with actually fit. The regulation was designed for foreign IT specialist hires within specific employment configurations, not for founders running their own IT operations. For founders, the work or investment residence pathways align with their actual configuration better than the narrow specialist-employee framework.

What's wrong with using IT residence anyway since I do IT work?#

The SDA reviews the application against Article 15(l)'s specific framework. Configurations that don't actually match the NACE/ISCO codes — even if they involve IT work in a general sense — will face refusal at the SDA. Refused applications close the IT residence pathway for that cycle and require restructuring into a different pathway. It's faster and cleaner to start with the right pathway than to file IT residence in error and pivot after refusal.

Can I be a foreign software developer running an IE for foreign clients and qualify under Article 15(l)?#

Almost certainly not — that configuration fits Article 15(a) work residence (IE economic activity for foreign clients) cleanly. Article 15(l) captures different configurations. The 1% Small Business Status IE configuration with foreign clients is the canonical work residence fit; trying to ground it under 15(l) instead would be misaligning the pathway with the actual operational profile.

Can I be a foreign founder of a Virtual Zone LLC and qualify under Article 15(l)?#

Most likely not — VZ LLC operations fit Investment residence (LLC-scale Georgian operations with operational substance, accelerated 5-year permanent residence track) much better than Article 15(l)'s specialist framework. The VZ LLC configuration is canonically an Investment residence fit, especially when the operations have demonstrable substance.

What if I'm hired by a Georgian IT company and I'm a foreign IT specialist?#

This is closer to the configuration Article 15(l) actually captures — foreign IT specialist employment by a Georgian employer. Even here, the qualification depends on the specific NACE/ISCO codes the regulation maps. The Residency Scoping walks through whether your specific role and qualifications match the framework. For foreign-employee configurations specifically, the work permit framework (with potential exemption under Article 13⁹ for International Company status holders) interacts with the residence permit decision and we work through both together.

How does IT residence interact with HNW Tax Residency?#

Like other residence permits, IT residence satisfies Layer 3 of HNW Tax Residency programme (residence permit). For foreign IT specialists pursuing HNW status, the IT residence permit (when 15(l) genuinely fits) grounds Layer 3 cleanly. Layer 1 (global wealth or income) and Layer 2 (USD 500,000+ Georgian assets, crypto excluded) need separate satisfaction. See HNW Tax Residency.

What if I want to switch from work or investment residence to IT residence later?#

Pathway switching is possible at renewal cycles when the qualifying configuration changes. Most foreign IT founders who consider switching to IT residence find the work or investment pathway they're already on actually fits their configuration better — the switch wouldn't improve their position. The Residency Scoping at switch time confirms whether the change makes sense; we don't recommend switches that don't actually serve the client's situation.

Can my family come on the IT residence permit?#

Family members typically need their own residence permits via family-reunification category (separate framework, grounded by their relationship to the primary holder). We coordinate family permits alongside the primary IT residence application when family relocation is part of the engagement.

How long does IT residence application take when Article 15(l) genuinely fits?#

For applications where 15(l) genuinely fits and the documentation is solid, typically 6–10 weeks from engagement start to first card. The longer end of the range covers cases where additional documentation of the specialist qualification is needed. Most reader configurations don't reach the application stage because the Residency Scoping concludes a different pathway fits better.

What's the typical Residency Scoping outcome for foreign IT founders?#

In our experience, most foreign IT founders' Residency Scoping engagements conclude with a different pathway recommendation — typically Work Residence (for IE+SBS foreign-client configurations) or Investment Residence (for LLC-scale operations). A small minority of cases where Article 15(l) genuinely captures the configuration proceed to IT residence application. The Residency Scoping is the dominant engagement; the application engagement is the exception.

Ready to assess?#

A free consultation maps your IT work configuration against Article 15(l)'s NACE/ISCO code framework and the alternative pathways (work, investment, property residence). For most foreign IT founders, the Residency Scoping concludes that a different pathway fits better than IT residence — and we say so honestly. For the minority of cases where Article 15(l) genuinely fits, we handle the IT residence application end-to-end. Most consultations resolve the pathway question in 30 minutes.