Applications arrive by email
The founder fills in a form, sends the attachments by email, someone copies them into a spreadsheet. Only that person knows which application sits at which stage; the week they are on leave, the centre goes blind.
A technology development centre's whole operation in one panel: founder applications, board reviews, office and rent, document verification, support tickets and KOSGEB reporting. Built for Alanya TEKMER, operated by us, now deployed for other centres.
Technology development centres run a very similar job in very different ways. The application form is a hosted form in one place and a PDF in another. Board decisions live in minutes. Rent tracking lives in a spreadsheet. The monthly KOSGEB report is what happens when all of that is assembled by hand. As the centre grows this setup does not break — it just comes to depend on one person.
TEKMER Portal puts that job in one place. The founder applies, the board reviews in the panel, management approves, office and rent run off the same record, documents are verified, support tickets progress on the record, and the data that goes to KOSGEB comes out of the centre's own system. Tenants get their own side of it too: company details, rent, receipts, employees and documents on their own screen.
We wrote the portal for Alanya TEKMER and we still operate it. Modules marked “Live” below are running in a real centre today. The ones marked “Add-on” come from our other service lines and connect to the panel: network and hotspot management, fingerprint and card access control, and a private file space for startups.
Almost every centre we talk to names the same four.
The founder fills in a form, sends the attachments by email, someone copies them into a spreadsheet. Only that person knows which application sits at which stage; the week they are on leave, the centre goes blind.
Preliminary, business-idea and executive board decisions sit in separate documents. When a revision is requested, what was written to the founder, whether the correction came back and who voted are never in the same place.
Who is in which room, when does the contract end, was this month invoiced, was the receipt uploaded. Three questions, three files, a phone call at month end.
Tenant, staff, project, support and exemption data sit in one shape in the centre’s own records and in another shape on the KOSGEB side. The monthly report means writing the same data a second time.
One deployment, one database, one permission model.
An eight-step form that changes with company type: separate required-field matrices for sole founder, sole proprietorship, limited and joint-stock companies. Bot protection, file upload and resume where you left off. Application number and account are created immediately.
Preliminary, business-idea and executive boards. Management assigns a reviewer; the member approves, rejects or asks for a revision. A revision goes straight back to the applicant, and the correction returns to the same board in a new round. Unanimity and a numbered decision PDF on the executive board.
An approved tenant gets an office and a room, rent and entry/exit dates are recorded, and the monthly invoice chain is generated. A company with several offices gets an invoice chain per office.
Management uploads the invoice, the tenant uploads the receipt, management approves. Only one active receipt per invoice; after approval the tenant cannot delete it. Paid, pending and upcoming months are separated by colour.
Company and employee documents kept apart: residence certificate, ID, tax registration, signature circular, trade registry, social-security records, centre contract. Which document is required from which company type is defined in the panel. Operational screens stay locked until the documents are verified.
Tenants book for themselves, management books in bulk. A cancellation reason is mandatory and recorded. Reminder notifications are sent by a background worker.
The tenant opens a ticket with photos, management replies, and it is closed with a stated reason. The category list is managed in the panel and an unanswered ticket closes automatically after a defined period. Notification and email at every step.
In-app notifications, queued email and SMS. Email delivery runs from a queue with three attempts; every send and its result is stored in the database.
The centre’s own site is managed from the same panel: tenant companies, team, events, gallery, FAQs, legislation, static pages and the contact form. The site updates as soon as the content changes.
One role-aware app for tenants, management, board members and applicants. A guest can apply from the app, a board member finishes a review on the phone, notifications arrive instantly.
One-click file and database backups from the panel, with progress and a retention window. Login attempts, status changes, every write request, email and SMS records are kept in separate tables.
Management, executive board, preliminary board, business-idea board, applicant and tenant. Each role sees only its own surface; permission checks run on the server, not in the screen.
KOSGEB's centre services expect the company, its staff, projects, grants, IP rights and exemptions each on their own endpoint. The portal already collects those fields; the integration is just sending what it has collected from the same record.
Every company in the centre has its counterpart on the KOSGEB side: create, update, list and delete endpoints are mapped. Company type is split into anchor company, centre tenant and founder.
Manager, specialist, technical, R&D, support and other staff types; education level, date of birth, start and end dates, social-security registration number, academic affiliation. The portal already collects these fields.
Project status is tracked as ongoing, completed successfully and completed unsuccessfully. Each project’s work-plan items and the staff assigned to them sit on their own endpoints.
Grants and loans received by the company; the granting institution and support programme are resolved from KOSGEB’s own parameter lists. One entry produces both the centre’s record and the KOSGEB record.
Examined and unexamined patents, utility models, industrial designs, geographical indications, integrated-circuit topographies, trademarks and software copyright. Each record is marked as an application or a registration.
R&D deduction, income-tax withholding incentive, social-security premium support, stamp-duty exemption and customs-duty exemption. Which company benefits from which exemption sits in one list.
The report is generated for a given month and year, viewed as a PDF and approved. The centre does not have to collect the underlying data by hand.
Access runs on JWT and is extended with a refresh token when it expires. Institution, support programme, country, university and university-department lists are pulled from KOSGEB’s own endpoints — no hand-written constants.
The monthly report is three steps: generate for a month and year, view the PDF, approve it if it is right. Nothing has to be tabulated by hand in between — the data is already in the portal.
Everything the periodic report asks for is already recorded before it is asked.
From application to board decision, from contract to office, from the operating period to graduation — each tenant’s timeline on a single page, with who changed what and when.
Investment amount, net sales revenue, export revenue and R&D spend — the four financial data types KOSGEB recognises. Entered per period, aggregated in the report.
Headcount and staff breakdown, with R&D staff separated from support staff. ID and social-security documents sit under the same record.
Patents, utility models, designs and trademarks across every tenant in one list, with application versus registration in its own column.
Work-plan items and their completion state. Ongoing, completed and unfinished items are the raw data behind the centre’s periodic report.
Login, booking, document, profile, office, rent and support events per company in one stream. "What did this tenant do in the last three months" is one screen.
The building's wireless network does not need a separate panel. Hotspot and firewall is a service line we already operate, and it connects to the tenant and office records in the portal.
The building’s wireless network connects to the portal: tenant staff sign in with their own account, visitors through verification. Who connected and when stays in the centre’s own panel.
Guest, tenant and management networks cannot see each other. Reaching one tenant’s machine from another’s device is closed at the network level.
Access records are timestamped and retained for the legally required window. Hotspot and firewall is already a service line we operate.
Bandwidth, time and content policy per person and per room are defined in the panel. A tenant leaving the building loses access when the contract ends.
In a centre, the answer to "who may enter which office, at what hours" is already in the portal. All the entry terminal has to do is read it.
Terminals on building and office doors connect to the portal. Authorisation lives in the centre’s tenant record, not in the device’s own list.
A per-day entry window can be defined for each tenant. The terminal reads that policy; the same rule is not maintained in two places.
Who entered, when, through which door, on behalf of which tenant. The record lands in the company activity feed and feeds the monthly occupancy report.
When an office assignment closes or a tenant graduates, card and fingerprint authorisation drops at the same moment. No separate trip to the terminal.
Tenant files sit in personal cloud accounts today, and the centre loses access to all of them the moment a tenant leaves. A file space on the centre's own storage closes that.
The tenant uploads files into its own space; the centre only sees shared folders. Document versions are kept and an accidentally deleted file can be restored.
Contracts, report templates, legislation and announcements are shared from the centre. The tenant drops its periodic report into the same folder — no more moving files by email attachment.
Expiring, password-protected share links. No separate service account needed to send a file to an investor or an advisor.
It runs on S3-compatible object storage and you choose which country the data sits in. Backups and restore tests stay with the same team.
The portal stores ID copies, signature circulars and social-security records. Security here is not a layer added afterwards; it is the sum of decisions taken up front.
A one-time code on top of the password. The code is never stored in the clear, attempts are counted, and the account locks temporarily on the fifth failure.
The session token is bound to a browser-specific fingerprint. A copied token is useless on another device, and suspicious reuse drops every session.
Role checks run on the server for every request. Hiding a button is not considered a control; an unauthorised request is refused before it is processed.
Every write request is recorded with user, address and timestamp. Who changed what, and when, can be asked afterwards.
Fields such as national ID numbers are stored encrypted. Which country the server sits in is written into the contract; Türkiye and Germany are both available.
File and database backups are taken from the panel with a defined retention window. Restores are tested on a schedule — a backup is only known to work once it has been tried.
A separate database and a separate domain per centre. Centres never share an installation; one centre’s data never touches another’s server.
Board structure, evaluation questions, document list, office and room layout, rent items and email copy are set to how the centre actually works.
Your spreadsheets and legacy panel data are moved over: tenants, contracts, office history and the document archive. A dry run comes first and the counts are compared.
Training for management and the boards, close support through the first period. Updates, monitoring, backups and technical support stay with the same team.
Technology development centres inside universities or chambers of commerce. The portal was written for this job, not adapted from another one.
Board, office, rent and periodic reporting work the same way. The KOSGEB module can be left switched off.
Company, office, access control and activity reporting map across directly.
Application, evaluation and support flows are ready, and the public website is managed from the same panel.
The portal already collects the fields KOSGEB expects — tenant company, staff, project, work plan, project staff, grants and incentives, intellectual property, exemptions — and we mapped them against the TEKMER API documentation. Sync is switched on with each centre’s own KOSGEB credentials during deployment and tested together; the IP allowlisting on the KOSGEB side happens at the same stage.
The portal already holds the policy for both: who is in which office and during which hours. The network build and the entry terminals are a separate line item; they come from the same team and connect to the panel. The portal also runs perfectly well on its own.
Each centre gets its own installation and its own database. The server can sit in Türkiye or Germany, you choose, and the choice goes into the contract. Fields such as national ID numbers are stored encrypted.
No, it is included. One app for iOS and Android; tenants, management, board members and applicants each see their own screens. Store submission is handled by us.
Yes. A migration is written for tenant records, contracts, office history and the document archive, a dry run is done first, counts are compared, then the real migration runs.
The number of boards, how members are assigned and the evaluation questions are all defined in the panel. Stage names and flow order are configured during deployment to match your regulations.
Deployment, configuration and migration are one-off; hosting, updates, monitoring and support are monthly. The figure depends on the number of tenants in the centre, so we need to talk about the size of your centre first.
Not in the standard package — the software is licensed and we keep operating it. Source transfer for a centre that has to continue with its own team is a separate contract.
More
Alanya TEKMER and the other brands we build software with.
Modules written on top of the portal for processes specific to a centre.
The team that writes and ships the portal's iOS and Android app.
Guest and tenant networks, VLAN separation and compliant logging.
The servers, monitoring and backups the portal runs on.
Tell us the size of your centre and we'll show you a live demo.
Book a free 30-minute discovery call with our team.
Our network and cyber security work is carried out by a team holding internationally recognised Cisco certification.
Issued by Cisco · Holder: Devrim Tunçer
A certification covering security operations centre (SOC) competency: security monitoring, incident response and analysis of network attacks. It is the foundation we rely on for intrusion detection, log correlation and post-incident response work.
Cisco training certificate · completed January 2023
Covers networking fundamentals: routing, switching, IP addressing and network security. The knowledge base we draw on for enterprise network setup and segmentation.