Custom Admin Panel Development with AdminJS

Note: when the standard admin panel is too rigid, and custom development is too expensive, AdminJS (see GitHub repository) offers a golden mean. But out of the box, it often doesn't cover complex business rules: custom actions, file uploads, role-based access. We have developed admin panels on AdminJS for e-commerce, logistics, and SaaS with over 20 projects under our belt. Once, for a retail chain, we implemented a custom action for bulk price changes — processing 5,000 products in 30 seconds. In this article, we'll share how to customize AdminJS, what tools we use, and where the boundaries of possibilities lie.

What problems does AdminJS solve?

AdminJS generates a CRUD interface based on data models. It is suitable for quickly launching an admin panel but requires refinement for non-standard scenarios. Here are the main challenges we address:

• Custom actions — bulk mailing, report generation, integration with external APIs. For example, for a logistics startup, we added an action to automatically create waybills, processing 10,000 records per minute.
• File uploads — via @adminjs/upload with S3 or local storage. We support auto-generation of previews and thumbnails for product images.
• Access rights — role-based and action-based (view, edit, delete). We configure a role model based on currentAdmin.role with cascading permissions.
• Custom components — replacing standard fields with React widgets: datepicker, autocomplete, WYSIWYG editors. For one client, we developed a warehouse selection component with geolocation.
• Performance — query optimization for tables with 100k+ records: adding indexes, using server-side filtering, connecting Elasticsearch for full-text search.

How to customize AdminJS for business requirements?

Stack: Node.js, TypeScript, React 18, AdminJS 7.x, TypeORM / Prisma. Deployment — Docker, Nginx, Vercel.

Consider an example: an online store with products, orders, and customers. Basic AdminJS setup with authentication and custom permissions:

import AdminJS from 'adminjs';
import AdminJSExpress from '@adminjs/express';
import { Database, Resource, getModelByName } from '@adminjs/typeorm';

AdminJS.registerAdapter({ Database, Resource });

const adminJs = new AdminJS({
    resources: [
        {
            resource: getModelByName('User'),
            options: {
                properties: {
                    password: { isVisible: { list: false, edit: false, filter: false, show: false } },
                    createdAt: { isVisible: { edit: false } }
                },
                actions: {
                    delete: { isAccessible: ({ currentAdmin }) => currentAdmin?.role === 'superadmin' }
                }
            }
        },
        {
            resource: getModelByName('Order'),
            options: {
                listProperties: ['id', 'customer', 'status', 'total', 'createdAt'],
                filterProperties: ['status', 'createdAt'],
                sort: { sortBy: 'createdAt', direction: 'desc' }
            }
        }
    ],
    dashboard: {
        component: AdminJS.bundle('./components/Dashboard')
    },
    branding: {
        companyName: 'My Store',
        logo: '/admin-logo.svg'
    }
});

const router = AdminJSExpress.buildAuthenticatedRouter(adminJs, {
    authenticate: async (email, password) => {
        const admin = await Admin.findOne({ email });
        if (admin && await bcrypt.compare(password, admin.passwordHash)) {
            return admin;
        }
        return null;
    },
    cookiePassword: process.env.COOKIE_SECRET
});

Custom component for displaying order status with color:

import { BasePropertyProps } from 'adminjs';

const OrderStatusCell: React.FC<BasePropertyProps> = ({ record }) => {
    const status = record.params.status;
    const colors = { pending: 'orange', completed: 'green', cancelled: 'red' };
    return <span style={{ color: colors[status] }}>{status}</span>;
};

export default OrderStatusCell;

Uploading product images to S3 via @adminjs/upload:

import uploadFeature from '@adminjs/upload';
import { s3Client } from './s3-client';

{
    resource: getModelByName('Product'),
    features: [
        uploadFeature({
            provider: { aws: { bucket: 'my-bucket', s3Client } },
            properties: {
                file: 'imageFile',
                filePath: 'imageUrl',
                filename: 'imageName',
                mimeType: 'imageMimeType'
            },
            uploadPath: (record, filename) => `products/${record.id()}/${filename}`
        })
    ]
}

Why does AdminJS save up to 60% time and budget?

Writing an admin panel from scratch on React and Express takes about 3–4 weeks for a typical CRUD. AdminJS reduces this to 1–2 weeks, which is 2-3 times faster. For projects with 10+ entities, time savings reach 60%, and consequently budget savings. When adding custom components, savings remain at 30–40%.

According to the official AdminJS documentation, the framework supports all popular ORMs and speeds up development by generating an interface from models. But it's important to understand: the out-of-the-box version provides basic functionality, and real savings come with proper configuration and customization.

What to do if AdminJS performance is unsatisfactory?

For tables with 100k+ records, standard mechanisms can slow down. We apply several approaches. First, server-side filtering: all filters are executed on the database side, not on the frontend. Second, indexing frequently queried fields. Third, avoiding find with loading all related entities; we use QueryBuilder with select only. In extreme cases, we connect Elasticsearch for full-text search.

Optimization example: in one project, an order table (200k records) opened in 5 seconds. After adding a composite index on (status, createdAt) and filtering by status, the load time dropped to 200 ms.

How we develop the admin panel?

1. Analysis — study data structure, business processes, access rights. Estimate scope in 1 day.
2. Design — define resources, actions, components, permission scheme.
3. Implementation — configure AdminJS, write custom components and actions, integrate with external services.
4. Testing — scenario verification, load testing (up to 10,000 requests).
5. Deployment and documentation — deploy on your server, provide instructions for administrators.

What is included in the result

• Fully functional admin panel on AdminJS with authentication.
• Custom components and actions as per your specifications.
• Integration with file uploads (S3, MinIO).
• Access rights differentiation (roles, actions).
• Source code, documentation, deployment instructions.
• 6-month warranty on identified bugs.

For simple projects, AdminJS reduces admin panel development time by 60% compared to writing from scratch. Contact us to discuss your project — get a consultation and preliminary estimate within 1 day. Order development of an admin panel on AdminJS.

Backend Development Services: Laravel, Node.js, Go, Django, PostgreSQL

On a production server at 3:14 AM, the Laravel Jobs queue stopped processing. 40,000 unprocessed jobs in Redis. Cause: worker crashed due to a memory leak in one of the Jobs (leak via a static variable in an Eloquent observer), supervisor didn't restart it because of misconfigured stopwaitsecs. This is not a hypothetical scenario — it's Tuesday. We analyzed such an incident on a project with 500 RPS load: diagnosis took 4 hours, fix — 20 minutes. So you don't lose money on downtime, we offer backend development services with a focus on production-grade reliability. We'll assess your project in 2 days.

Backend is what works when no one is watching. Or doesn't work. We guarantee you'll have the first option.

How do we ensure production-grade reliability from day one?

What we do correctly from day one

Service Layer over Fat Controllers. Controller receives HTTP request, validates it via Form Request, passes data to Service, returns response. Business logic in Service, not Controller. This sounds trivial, but most legacy projects have controllers with 500 lines and SQL queries inside.

Repository Pattern we use cautiously. If you just wrap Model::where(...) in a repository method — that's boilerplate without benefit. Repository is justified when: you need to abstract from the data source (DB + cache + external API) or when query logic is complex enough to isolate.

Jobs, Events, Listeners. Everything that can be async — make async. Sending email, PDF generation, external API sync, aggregate recalculation — into Queue. Laravel Horizon for queue monitoring in Redis: see throughput, failed jobs, processing time per queue.

How Octane handles high load

Laravel Octane with RoadRunner or Swoole keeps the app in memory between requests — removes bootstrap overhead (config loading, class autoloading) on each HTTP request. Gain: 3–8x on synthetic benchmarks, 2–4x on real applications. Important: no state between requests in static variables — that leads to exactly the incidents from the beginning. We use this in projects with >1000 RPS.

What to do about N+1 queries

N+1 is the most common cause of slow pages in Laravel apps. Standard story: page worked fine on dev with 10 records, on production with 10,000 — 8-second load.

Laravel Debugbar in dev environment shows the number of queries per page. More than 20 queries per page — signal for audit.

Model::preventLazyLoading(! app()->isProduction());

Telescope for profiling in staging: logs all queries, jobs, mail, notifications with time detail. Numbers: after implementing eager loading, page load time drops from 8s to 0.3s — 27 times faster.

PostgreSQL: indexes that are actually needed

PostgreSQL 14+ is the primary DB on all projects. We use PgBouncer + PostgreSQL combination. 10+ years experience, more than 50 backend projects, 5 years on the market.

How PostgreSQL helps avoid slow queries

Composite indexes for frequent WHERE + ORDER BY. If you have WHERE user_id = ? AND status = ? ORDER BY created_at DESC — you need (user_id, status, created_at DESC). A separate index on (user_id) doesn't help much with sorting.

Partial indexes. If 95% of queries go with WHERE status = 'active':

CREATE INDEX idx_orders_active ON orders (created_at DESC)
WHERE status = 'active';

The index is small, fast, covers the main load.

GIN indexes for JSONB and arrays. @> operator without GIN index — seq scan. With index — fast even on millions of rows.

GIN for full-text search. to_tsvector + GIN instead of LIKE '%query%'. LIKE without index is always seq scan. With pg_trgm extension and gin_trgm_ops — supports LIKE with index, useful for CRM search by partial match.

Connection pooling: why it's more important than it seems

Rails, Laravel, Django open a new connection to PostgreSQL for each PHP/Python process. With 100 workers — 100 connections. PostgreSQL starts degrading from 200–300 active connections — overhead on connection management becomes significant.

PgBouncer — connection pooler in front of PostgreSQL. Transaction pooling mode: connection to PostgreSQL is occupied only during a transaction, returned to pool between requests. 1000 application workers → 20–50 actual connections to PostgreSQL. This reduces latency by 40% and hosting costs by 30%.

Node.js with Fastify: when it's better than Laravel

Node.js is justified for:

• Realtime: WebSocket servers, Server-Sent Events, chat, live updates
• Streaming: large files, video, streaming data
• High I/O concurrency: many parallel requests to external APIs without heavy business logic
• Serverless: Lambda/Cloud Functions — Node.js starts faster than PHP

Fastify over Express: 2–3 times faster on benchmarks, built-in JSON Schema validation, better TypeScript support, plugin architecture.

Typical realtime architecture: Laravel — core business logic and REST API. Node.js + Socket.io or ws — WebSocket server. Laravel publishes events to Redis Pub/Sub, Node.js subscribes and broadcasts to clients. This separation allows scaling the WebSocket server independently of the main app.

Go: microservices and high load

Go we use for:

• High-load microservices (>10,000 RPS)
• Background workers with strict latency requirements
• DevOps tools and CLI
• gRPC services in microservice architecture

Goroutines — thousands of times cheaper than OS threads. 10,000 concurrent connections on Go is normal on one server.

But Go is not a silver bullet. Development is slower than Laravel: more boilerplate, no ORM at Eloquent level, error handling with if err != nil everywhere. Justified only when performance is a real requirement, not an assumption.

Django and Python backend

Django with DRF (Django REST Framework) — for tasks where Python is needed: ML pipelines, data processing, integrations with AI tools.

Celery for background tasks — similar to Laravel Queue but more complex to configure. Celery Beat for cron tasks.

Django ORM vs raw SQL: ORM is convenient for CRUD. For analytical queries with multiple JOINs, window functions, and CTEs — connection.execute() with raw SQL is more readable and predictable.

Redis: not just cache

Redis in our projects plays multiple roles:

Redis Cluster for horizontal scaling. Sentinel for automatic failover on standalone setups.

Deployment and infrastructure

Docker + docker-compose — standard for local development and production. Each service in a container: PHP-FPM/Octane, Nginx, PostgreSQL, Redis, Queue Worker, Scheduler.

CI/CD via GitHub Actions:

1. Run tests (PHPUnit / Pest, Vitest, Playwright)
2. Build Docker image
3. Push to Container Registry
4. Deploy: docker pull → docker-compose up -d on server, or Kubernetes rolling update

Zero-downtime deploy for Laravel: php artisan down --secret=TOKEN is not needed with proper configuration. Strategy: new container starts next to the old one, Nginx switches traffic after health check, old container stops.

Monitoring: Sentry for exception tracking with alerting in Slack/Telegram. Grafana + Prometheus (or Grafana Cloud) for metrics: CPU, memory, request rate, queue depth, database connection count. Alerts on: error rate > 1%, p99 latency > 2s, queue depth > 1000 jobs.

What's included in turnkey work

• Architecture design (API documentation, DB schema, service diagram)
• Implementation according to agreed specification with code review
• CI/CD, monitoring, alerting setup
• Load testing (k6, wrk) with report
• Handover of source code, access, deployment instructions
• Training of customer's team (2-3 sessions)
• Warranty support for 1 month after delivery

Timeline benchmarks

Pricing is calculated individually after analyzing load, integrations, and business logic. Contact us for a free audit of your current backend — get an optimization plan in 2 days. Request a consultation.