The Nokia 6300 went on sale in early 2007. It has a 240 by 320 pixel screen, a numeric keypad, no touchscreen, no Wi-Fi and a 2G radio. It cannot load Google anymore. As of this month, it can ask Claude what is happening in the news and get an answer with sources.
The app that makes it happen is called AIKON, which is Nokia spelled backwards. It was built by Turkish developer Emir Karsiyakali, who started it in late September as a Claude-only experiment called Claude S40. Within weeks it grew support for ChatGPT, Gemini and Grok, picked up a paid hosted version, and landed on the front page of tech sites this week after TechRadar wrote it up.
It is a genuinely clever piece of work. It is also a neat case study in what you have to give up to make a 19-year-old phone talk to a 2026 server. The answer is: quite a lot of what modern encryption assumes.
What AIKON actually does on a keypad phone
The obvious expectation is a bare text box. AIKON is a lot more polished than that. The developer’s GitHub page lists a feature set that would not look out of place in a smartphone app, squeezed into a Java file of about 220KB.
| Feature | How it works on a 2007 phone |
|---|---|
| Model picker | Choose Claude, OpenAI, Gemini or Grok per chat and switch mid-conversation. Every reply is labeled with the model that wrote it. |
| Web search | Runs on the server through each provider’s own search tool, so the phone’s ancient browser is never involved. Sources appear under the answer. |
| Photos | Takes a 640 by 480 snapshot with the phone camera, or picks a file up to 1MB. Useful for “translate this sign” or “read this label”. |
| Voice messages | Records up to 30 seconds, transcribes it on the server, and drops the text into the editor so you can fix it before sending. |
| Calendar and to-do | Say “dentist tomorrow at 3” and the reply carries a ready entry. Nothing is written to the phone’s calendar until you press Save. |
| Reading mode | Pages through long answers one screen at a time, with three text sizes and light or dark themes. |
| Offline saves | Stores any answer as a .txt file on the memory card for reading without a connection. |
| Languages | Menus in English, Turkish, Spanish, Portuguese, French, German, Russian and Indonesian. Answers follow whatever language you type in. |
Every screen is designed for the keypad. Number keys select messages, the center key opens actions like “shorten”, “explain more simply” or “translate”, and a shortcuts screen lists every key. Message actions only fill in the editor. Nothing paid is sent until you press Send, and a retry after an error never charges twice.
The developer has tested it on two phones: the Nokia 6300 (Series 40) and the Nokia E63, a Symbian S60 phone with a QWERTY keyboard. Other Series 40 handsets with Java ME (CLDC 1.1 and MIDP 2.0) and a 240 by 320 screen may work, but they are officially untested.
The hard part was never the AI. It was the handshake.
Getting a chatbot answer onto a small screen is easy. Getting the phone to open a secure connection to a modern server is the problem, and AIKON’s architecture notes explain exactly why.
When the developer measured what a Nokia 6300 sends when it tries to connect, the answer was a museum piece. The phone offers only TLS 1.0, the encryption standard from 1999 that the IETF formally deprecated in 2021. It sends no SNI, the bit of information modern servers use to decide which certificate to show. Its cipher list includes RC4 and 3DES, both long considered broken or obsolete. And its built-in list of trusted certificate authorities stops at roughly 2008, with VeriSign, Thawte, Equifax and GeoTrust roots that have since expired or been distrusted.
That combination means a big CDN like Cloudflare rejects the phone before it even sends a certificate, and no public certificate authority today issues anything the phone would trust. AIKON’s fix is to cut the modern internet out of the first hop entirely.
The AIKON server terminates the connection itself, using an RSA-2048 certificate signed by a private root certificate authority that you save on the phone once. The server is strict about what it accepts: no RC4, no 3DES, and no plain HTTP for the app. The phone ends up negotiating AES-128 with SHA-1, which is about the best a 2007 Nokia can do. From the server onward, your messages travel to the AI providers over normal, modern HTTPS.
Installing a root certificate is a bigger deal than it sounds
Here is the part of the setup that the excited social posts skip over. To use the hosted service, you open m.aikonchat.com in the phone’s browser and accept a security certificate. The site publishes its SHA-1 fingerprint so you can check it, which is good practice. But it helps to understand what you are agreeing to.
A root certificate is not a permission for one app. It is a statement to the phone that says “trust anything this authority vouches for”. It is the same mechanism companies use when they install their own root on work laptops so they can inspect encrypted traffic, something we covered in our guide to what your employer can see on work Wi-Fi. In principle, whoever controls that private authority could vouch for other sites too.
There is also the question of who sees your chats. AIKON’s privacy notice is short and fairly clear. The hosted service is run by Moneo Software LLC, a Wyoming company. The server sits in Frankfurt on DigitalOcean. Your messages, photos and the text of voice messages go to whichever AI company you pick. Chats are stored for 30 days after the last message, pinned chats until you delete them, and voice audio is not kept. Server logs, the notice says, contain no message text, codes or IP addresses. Card payments go through Stripe and never touch AIKON’s server.
That is a reasonable setup for a hobby project turned micro-business. It is still one extra company between you and the chatbot, compared with using the ChatGPT or Claude app directly.
What a message costs on a Nokia
The open source code is free. The hosted service is not, because someone has to pay the AI companies. The developer’s announcement on X says new users start with a free trial, then buy credits. There are three packs:
- 5,000 credits for $4.99
- 11,000 credits for $9.99
- 24,000 credits for $19.99
Credits are charged by message length and model, and AIKON publishes rough costs for a short message without web search. Failed requests are free. Here is what the cheapest pack buys you with each model.
For perspective, that makes a casual question cheaper than a 2007 text message in a lot of countries. Heavy use adds up quickly, though. Web search, photos and long back-and-forth chats all burn more credits, and the per-message figures above are the floor, not the average. The refund policy is simple: if you have not entered your code on a phone yet, you can ask for your money back within 14 days.
The American problem: your 6300 has no network to join
If you live in the US and have a Nokia 6300 in a drawer, there is a catch that has nothing to do with AIKON. The phone connects to the internet through 2G GSM data, and it has no Wi-Fi. That network is gone.
AT&T turned off its 2G network at the start of 2017. T-Mobile held on far longer to support legacy devices, but its final GSM signal went quiet on August 3, 2026. Verizon never ran GSM at all. So in the US, a stock Nokia 6300 can boot, run AIKON, and show you a connection error.
The workaround is to pick a different old phone. The developer also tested AIKON on the Nokia E63, which has built-in Wi-Fi, and connected it over WLAN. Wi-Fi equipped Symbian phones from that era are the realistic choice for American tinkerers. Countries that still run 2G networks, including much of Europe, Turkey and parts of Asia and Africa, are in a better spot for the 6300 itself.
Hosted service or your own server?
Because AIKON is open source on GitHub, you are not forced to use the paid service. The developer originally only offered the code, then built the hosted version because, in the developer’s words, most people gave up at the setup steps. Here is how the two options compare.
| Hosted (aikonchat.com) | Self-hosted (GitHub) | |
|---|---|---|
| Setup | Open a URL on the phone, accept the certificate, install the app, type a code | Docker host, generate your own root CA, build the Java app, pair the phone |
| Monthly cost | Pay per message with credit packs from $4.99 | A $4 to $6 VPS plus your own API bills |
| Who holds the root CA | Moneo Software LLC | You |
| Who stores your chats | AIKON server in Frankfurt, 30 days | Your own SQLite database |
| Best for | Trying it for fun in ten minutes | Developers and the privacy-minded |
The self-hosted server even starts in a test mode that returns fake replies at no API cost, so you can get the phone paired before you plug in a real key. The quick-start guide is a handful of shell commands for anyone comfortable with a terminal:
git clone https://github.com/emir/AIKON.git
# 1. Create your own private root CA and server certificate
server/scripts/pki.sh ca ~/.config/claude-s40/pki
# 2. Deploy the Go server (starts in free test mode)
server/deploy/push.sh root@your-server --execute
# 3. Build the phone app and install AIKON.jad / AIKON.jar
make -C appWhy a chatbot on a dumb phone is more than a stunt
It is easy to file AIKON under “fun weekend hack”, and the developer clearly enjoyed making it. The project’s own tagline is that a 2007 Nokia cannot search Google anymore, so the developer gave it Claude instead. But there is a real idea underneath.
Old feature phones are dead ends today not because the hardware stopped working, but because the web moved to encryption and page sizes those phones cannot handle. AIKON shows that a thin client plus a server can bring a lot of usefulness back: current news, translation of a street sign, a quick calendar entry. It is the same pattern big phone makers are now chasing on purpose. HMD’s latest Nokia-branded feature phones ship with a dedicated AI key, a move that did not go over well with buyers who chose those phones to get away from exactly this kind of thing.
AIKON is also a good example of where vibe coding with AI assistants is heading. A single developer went from a Claude-only demo to a multi-model, eight-language app with payments in about a month. That is the same trend that has Google letting people run private, vibe-coded apps on their own Android phones. The difference is that this one runs on hardware that predates the iPhone.
Should you try it?
If you have a supported Nokia that can actually get online, and you treat it as a curiosity, yes. It costs five dollars to find out, there is a free trial first, and the engineering is genuinely impressive. Just accept the certificate only on a phone you do not use for anything else, check that SHA-1 fingerprint, and remember that a keypad and a 2-inch screen are still a keypad and a 2-inch screen.
If you want a minimalist phone that can still ask an AI a question, AIKON is a proof of concept, not a daily driver. And if you are in the US with a 6300, the most important accessory is not a credit pack. It is a phone with Wi-Fi.
Models: Claude, ChatGPT, Gemini, Grok
Price: free trial, then $4.99 / $9.99 / $19.99 credit packs, or free to self-host
Data: server in Frankfurt, chats kept 30 days, voice audio not stored
Affiliation: independent project, not affiliated with Nokia, Anthropic, OpenAI, Google or xAI
About this article: GeekBlog covers U.S. technology news, AI, phones, smartwatches and gaming. Every story is written and checked under our Editorial Policy. Spotted a mistake or have a story tip? Contact our editors.
